What the Data for This Category Looks Like
Typical data for this category comes from state-owned assets supervision information systems, enterprise asset management systems, property rights exchange systems, evaluation agency reports, and financial statements. Daily documents include property rights registration forms, asset evaluation reports, property rights transfer plans, on-site transaction announcements, and asset disposal approval documents. These documents contain fixed fields such as ownership identifiers, asset parameters, and approval process nodes. The data update frequency is monthly. Document volume varies widely. Some asset evaluation reports or on-site transaction announcements are lengthy, with individual documents reaching thousands of characters.
Constraints on Knowledge Base Retrieval and Recall
Multi-source and heterogeneous data sources require the retrieval link to support document formats exported from different systems. This prevents loss of core field information such as ownership numbers and approval document numbers due to format differences. The monthly update frequency requires the knowledge base synchronization mechanism to align with the business cycle. This prevents use of expired asset ownership or transaction data. Long documents and image-containing report content require retrieval and recall to support long text chunking and image-associated recall. This ensures key information is not truncated. The high-risk nature of state-owned asset disposal requires retrieval results to accurately match business scenarios. This prevents mismatched ownership information or missing process nodes, which could lead to serious consequences such as loss of state-owned assets.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Matches the precision requirement for core fields such as property rights ownership and approval nodes, to avoid mixing irrelevant asset data with low similarity into results |
limit | Top 8–12 entries | A single retrieval must cover multiple associated documents, such as transfer plans, approval documents, and announcements, to ensure complete materials required for the business process |
searchMode | Full-text retrieval | Adapts to long document and multi-field matching requirements, and can accurately locate key business information such as asset numbers and approval document numbers |
usingReRank | Enabled | Performs secondary ranking on initially recalled results, to prioritize returning approval nodes or ownership descriptions that are strongly related to the business handling process |
datasetSearchUsingExtensionQuery | Enabled | Performs expansion optimization on user queries, supplementing industry common terms such as "asset disposal process" and "property rights transfer conditions", to improve recall coverage |
collectionIds | Specify the exclusive dataset ID for property rights and assets | Isolates business data, to avoid interference from irrelevant documents on retrieval results, and ensure that recalled content only comes from compliant data sources of this category |
Three Common Configuration Mistakes
- Phenomenon: Image-containing asset evaluation reports added to the knowledge base cannot be displayed properly after retrieval. Cause: The image parsing configuration is not enabled, and the text description associated with the image is not correctly extracted during document parsing.
- Phenomenon: DOC format property rights registration forms or asset disposal approval documents cannot be imported directly. Cause: The document format compatibility conversion capability is not configured, or the parsing support for the corresponding format is not enabled.
- Phenomenon: Expired asset ownership data appears in retrieval results. Cause: The knowledge base synchronization cycle does not match the monthly update requirement, and the latest state-owned assets supervision system data is not synchronized in a timely manner.
How to Confirm Proper Configuration
- Upload a standard property rights registration form document, and check whether core fields such as ownership number and original asset value are retained after parsing.
- Initiate a query related to the asset disposal process, and verify that the number of returned results falls within the preset
limitvalue range. - View the knowledge base synchronization log, and confirm that the most recent synchronization completion time is within the monthly update cycle.
- Test the retrieval results after enabling
usingReRank, and confirm that highly relevant approval process documents appear at the top of the results.
The values provided here are common starting points, and should be evaluated 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.