What This Category’s Data Looks Like
Typical entities for this category include natural resources departments, state-owned asset supervision institutions, public resource trading centers, and similar organizations. Daily documents cover transfer announcements, trading notices, bid application materials, margin vouchers, transaction confirmation letters, listing result announcements, property rights transfer descriptions, and other related documents. Data comes primarily from national public resource trading platforms, natural resource trading systems, property rights exchange systems, and state-owned asset supervision systems. Update frequency is daily. Documents are categorized by business stage into announcement-type, application-type, and voucher-type. Core fields include trading subject ownership information, margin amount, bid qualification requirements, transaction confirmation number, and other key details.
Constraints on Knowledge Base Retrieval and Recall
Multi-source heterogeneous data sources require the retrieval link to associate multiple dedicated datasets, to avoid interference from cross-category content. Daily update frequency requires configuring automatic synchronization rules to ensure timeliness of policy documents and transaction vouchers. Core retrieval priorities vary significantly across different document types. For example, ownership information requires precise matching, while margin clauses require full recall. Retrieval logic must therefore distinguish document weights. Errors in transactions for this category can lead to invalid transactions, disputes over state-owned asset loss, or blocked property transfers. As a result, recall results must have high confidence, filter low-relevant content, cover key business fields, and avoid risks caused by missing policy clauses.
Configuration Settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Used for policy basis retrieval, filters low-relevant results, avoids mismatched ownership information, balances recall coverage and precision |
limit | Top 10 entries | Covers multiple associated policy documents in the transaction process, while controlling context length to avoid exceeding model processing limits |
searchMode | Vector + keyword hybrid | Balances semantic matching of policy text and precise hits for keywords such as "land use rights" and "mining rights", adapting to multiple types of policy documents |
usingReRank | Enabled | Reranks recall results, prioritizes content containing core business fields such as ownership, margin, and transaction confirmation |
datasetSearchUsingExtensionQuery | Enabled | Automatically expands synonyms related to policies, such as expanding "state-owned property rights trading" to "enterprise property rights transfer" and "property rights listing", improving recall coverage |
collectionIds | Configured by business module | Separately associates dedicated datasets for land use rights, mining rights, and state-owned property rights transactions, preventing cross-category content from mixing into retrieval results |
Three Common Configuration Errors
- Retrieval results include non-target category policy documents. Cause: The
collectionIdsparameter is not used to specify dedicated datasets, resulting in recall of all public resource trading-related content in the full knowledge base. - Transaction voucher files cannot be downloaded normally after clicking "View Original Content". Cause: The original file download link configuration is not retained, or the original file path is not correctly associated after file parsing.
- Key ownership restriction clauses are missing from retrieval results. Cause: The
similaritythreshold is set too high, filtering policy segments with medium semantic relevance but containing core ownership information.
How to Verify Configuration Validity
- Input the query "policy basis for land use rights transfer", confirm that all recall results are land-related documents to verify the
collectionIdsconfiguration takes effect. - Select the "View Original Content" button for any retrieval result, confirm that the corresponding transfer announcement or transaction confirmation letter file can be downloaded normally.
- Adjust the
similaritythreshold, observe changes in the relevance of retrieval results to verify that parameter configurations take effect. - Test transaction files pushed by external systems, confirm that automatic parsing and chunking are completed and the files can be retrieved, to verify that synchronization configurations take effect.
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.