What data for this category looks like
Typical data subjects for this category include development and reform departments, industry competent departments such as housing and urban-rural development, transportation, and water resources, public resource trading centers, and bidding agencies. Data sources include national public resource trading platforms, local trading platforms, engineering approval systems, and bidding supervision systems. Update frequency is daily. Daily documents cover bidding announcements, pre-qualification documents, tender documents, bid documents, evaluation reports, successful bid candidate announcements, and successful bid result announcements. Core fields include bid section information, qualification requirements, bill of quantities, evaluation records, and project cycles.
Constraints on knowledge base retrieval and recall workflows
Multi-source heterogeneous data sources require the retrieval system to support document formats from different platforms, to prevent partial data from failing to be retrieved due to inconsistent formats. Daily update frequency requires configuring incremental synchronization logic, to avoid performance loss from full retrieval. Core fields of bidding documents such as bid sections and qualification requirements are highly specialized, so precise field matching must be prioritized to prevent irrelevant project data from being introduced via fuzzy retrieval. Additionally, errors in bidding operations have serious consequences, so retrieved results must have high confidence to avoid incorrect information affecting inquiries and responses.
How to set configurations
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Bidding documents have a high proportion of specialized terminology. This threshold filters low-match irrelevant results and ensures the accuracy of inquiry responses |
limit | Top 8 entries | Core content of bidding inquiries focuses on limited dimensions such as bid sections and qualification requirements. A small number of results avoids information overload |
searchMode | Precise matching mode | Fields such as bid section numbers and qualification requirements in bidding documents must strictly correspond. Precise matching avoids invalid retrieval across projects |
usingReRank | Enabled | Bidding documents contain a large number of industry-specific terms. Reranking corrects the initial retrieval order and prioritizes content related to qualification requirements and evaluation rules |
datasetSearchUsingExtensionQuery | Enabled | User inquiries often use colloquial expressions. Extended queries can associate with standard fields in official announcements and cover more potential inquiry scenarios |
collectionIds | Bind corresponding datasets by business domain | Bidding data is isolated by project domain. Binding dedicated datasets avoids introducing irrelevant information during cross-project retrieval |
Three common configuration errors
- Issue: The knowledge base cannot retrieve specified bidding announcement content. Cause: The dataset for the corresponding public resource trading platform is not bound to the
collectionIdsconfiguration, or thesimilaritythreshold is set too high, filtering valid matching results. - Issue: Knowledge base training fails, showing core fields as empty. Cause: Key information such as bid sections and qualification requirements is not split, and core business content is lost after chunking, preventing normal retrieval.
- Issue: Retrieval requests time out. Cause: Incremental update logic is not configured. Full retrieval of newly added daily bidding data takes too long, exceeding the system's response limit.
How to confirm configurations are correctly set
- Retrieve the bidding announcement for a specified bid section, confirm that returned results include core fields such as qualification requirements and bill of quantities for that section.
- View the dataset update log, confirm that the latest announcements from public resource trading platforms are automatically synchronized daily, and the update frequency meets business requirements.
- Test colloquial inquiries such as "What are the evaluation criteria for this project", confirm that returned results are associated with the evaluation report content of the corresponding tender document.
- Adjust the
similaritythreshold, verify that the number of retrieved results matches the expected configuration across different thresholds.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.