Reference only; verify against the target FastGPT release and deployment documentation.
What this category of data looks like
Typical entities include natural resources authority land use control and planning permission offices, administrative examination and approval bureaus, and project units. Daily documents include land pre-examination and site selection opinions, construction land planning permits, construction engineering planning permits, red line drawings, and planning conditions. Data sources include the national spatial planning one-map system, project examination and approval supervision platform, land use status database, and ecological protection red line data. Update frequency is irregular. Documents contain fields such as project subject, site selection scope, control requirements, and approval document number. The structure varies across different document types.
What constraints do these characteristics impose on citation source and traceability
Since data sources span multiple systems, traceability workflows must associate and map identifiers across sources. Daily documents cover multiple types with varying field structures, so traceability must adapt to field mapping rules for different document types. Data updates occur irregularly, so a regular synchronization trigger mechanism must be configured. Errors can lead to severe consequences, so citation sources must be traceable to prevent incorrect citations from delaying project approval or blocking construction startup.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
quoteMaxToken | 800–1200 characters | Aligns with the length of documents related to land pre-examination and planning permits, avoiding truncation of critical information such as approval document numbers, red line ranges, and control requirements |
responseData | Structured format including citation sources | Ensures citation information can be extracted and displayed by the system, meeting traceability display requirements |
detail | Enabled | Used to display complete citation source details, including data sources, document numbers, and other content |
| Single recall limit | Top 5 entries | Matches the number of associated project examination and approval data, avoiding returning redundant non-core associated content |
| Context window | Calibrated via actual testing | Adapts to the association needs of multi-source data, ensuring recalled information covers core examination and approval related content |
| Knowledge base synchronization frequency | Follow business update rhythm | Adapts to the irregular update feature of data, ensuring knowledge base content aligns with latest policies |
Three Common Mistakes
- Phenomenon: The response body does not include associated content from the local knowledge base, but correct knowledge base entries appear in the citation list. Cause: The
detailparameter orresponseDataformat is not configured correctly, preventing citation information from being integrated into the response body. - Phenomenon: Citation information for private knowledge bases cannot be retrieved when calling external APIs. Cause: Associated permissions for external calls are not configured, or
responseDatais not set properly to support external data extraction. - Phenomenon: Relevant data from the national spatial planning one-map system cannot be associated during traceability. Cause: Field mapping rules for multi-source data are not configured, causing fields from different data sources to fail to match correctly.
How to Verify Proper Configuration
- Initiate a query containing keywords related to land pre-examination and planning permits, and check whether the response body includes citation source annotations.
- View the citation list below the response, and confirm that each citation's source, document number, data scope, and other information align with business facts.
- Call the external API interface, and check whether the returned results include structured citation information.
- Manually trigger a knowledge base synchronization, and check whether the synchronization task status is normal and data updates follow the expected rhythm.
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.