What this category of data looks like
Typical data sources for this category include national public resource trading platforms, local public resource trading platforms, project approval systems, and bidding and tendering supervision systems. The update frequency is daily. Daily documents cover tender announcements, pre-qualification documents, bidding documents, bid submission documents, bid evaluation reports, successful bid candidate public notices, successful bid result announcements, and more. Fields included are project number, section information, qualification requirements, bid evaluation expert records, public notice period, and others. Involved entities include development and reform departments, industry competent departments such as housing and urban-rural development, transportation, water conservancy, public resource trading centers, and bidding agency institutions.
What constraints do these characteristics impose on the "citation sources and traceability" link
Multiple platform data sources create format differences, requiring adaptation to document structures and field naming rules of different platforms. The daily update feature requires configuring incremental synchronization mechanisms to ensure recalled content covers the latest bidding, bid evaluation, and public notice information. Diverse document types and professional content require chunking and recall to match the core information dimensions of different documents. Traceability must accurately correspond to specific document entries and paragraphs, otherwise it may lead to incorrect bid evaluation basis, disputes over bid winning results, and other negative outcomes.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 token | Engineering bidding documents have long single content, requiring coverage of complete qualification conditions, bid evaluation rules, or successful bid result details |
responseData | Enabled | Needs to associate the filed field of the corresponding document to achieve accurate traceability |
detail | Enabled | Needs to display specific paragraphs, document types, and release times of source documents |
| Single recall limit | Top 5–7 entries | Bidding-related questions need to cover multiple types of documents such as announcements and bid evaluation reports; excessive recall will dilute answer relevance |
| Similarity threshold | 0.72–0.85 | Balances recall accuracy and coverage, avoiding missing key bid evaluation basis or introducing irrelevant content |
Three Common Misconfigurations
- Phenomenon: After adjusting the single recall limit parameter, the number of recalled content does not change, remaining at a fixed value. Cause: The incremental synchronization rule of the bidding data source is not correctly configured, causing the recall pool to not update with parameter adjustments.
- Phenomenon: The output content retains Markdown source code format and is not rendered into a readable document structure. Cause: The format rendering switch for response content is not enabled, and the original chunked Markdown text is returned directly.
- Phenomenon: The filed field displayed in the traceability source is empty, and cannot be associated with a specific document entry. Cause: The filed field was not correctly extracted and stored when uploading bidding documents, or the field name for traceability association was not specified in the configuration.
How to Verify Proper Configuration
- Submit a test question involving bid evaluation qualification conditions, check whether the source annotation of the returned result includes the corresponding document type and number.
- Adjust the
quoteMaxTokenparameter value, check whether the length of recalled content changes with the parameter. - Upload a test tender announcement document, verify that the traceability field can correctly associate with the uploaded file.
- Trigger an incremental synchronization task, check whether newly added bidding documents can be normally recalled.
The values provided here are common starting points, and should be evaluated against the user'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.