Reference only; verify against the target FastGPT release and deployment documentation.
What data for this category looks like
Daily documents for this category include transfer announcements, transaction notices, bid applications, margin vouchers, transaction confirmation letters, listing result announcements, and property transfer descriptions. Data sources are national public resource trading platforms, natural resource trading systems, property exchange systems, and state-owned asset supervision systems. Update frequency is daily. Documents typically include fields such as target ownership information, transaction restriction conditions, margin requirements, and transaction process nodes. Some documents contain quantitative content like plot area and transaction amount. The overall structure is centered on transaction processes, covering all materials from listing to finalization of the transaction.
What constraints these characteristics impose on knowledge base retrieval and recall
Multi-source heterogeneous data sources require retrieval to support joint recall across cross-system datasets. The daily update frequency requires configuring real-time synchronization mechanisms to ensure data timeliness. Documents focus heavily on high-constraint fields such as ownership and transaction rules. Errors here directly relate to state-owned asset interests, so retrieval must prioritize high-match result recall. This category’s documents differ significantly from general procurement documents. Retrieval results must not include irrelevant procurement project materials, so retrieval scope must be strictly limited to datasets related to public resource trading.
How to set configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.72–0.80 | This category requires precise matching of core fields such as ownership and transaction rules. A threshold that is too low will introduce irrelevant documents, while a threshold that is too high may miss valid reference content |
limit | Top 8–12 results | Balances context length and information completeness, avoiding overload from single-round retrieval that reduces document drafting efficiency |
searchMode | hybrid | Combines vector semantic and keyword matching, adapting to mixed retrieval needs for structured fields like ownership numbers and transaction amounts, as well as rule text |
usingReRank | Enabled | Addresses the long-text characteristics of transaction documents. Reranking improves the ranking priority of highly relevant results |
datasetSearchUsingExtensionQuery | Enabled | Automatically expands retrieval terms to cover synonymous expressions for high-frequency documents such as bid applications and transaction confirmation letters |
collectionIds | Specified by business domain | Limits retrieval scope to exclusive datasets for land use rights, mining rights, or state-owned property transactions, avoiding interference from cross-category irrelevant data |
Three common mistakes
- Using an application key when calling the knowledge base retrieval interface returns a 403 permission error. This occurs because the exclusive key for the target dataset is not used, or access permissions for the dataset are not enabled in platform configurations.
- Attempting to limit retrieval scope via the
collectionIdsparameter without effect. This happens because the corresponding switch for specified collection retrieval is not enabled in the retrieval configuration, or the parameter format does not meet interface validation rules. - Not organizing uploaded documents into folders by transaction type, leading to retrieval results including materials from non-target categories. This occurs because the folder structure is not understood as a way to divide datasets by business domains such as land, mining, and property, making precise filtering of retrieval scope impossible.
How to confirm configurations are correct
- Call the retrieval interface and pass the specified
collectionIdsparameter, verifying that returned results only include documents related to land use rights, mining rights, or state-owned property transactions. - Check the knowledge base synchronization logs to confirm that latest documents from national public resource trading platforms and natural resource trading systems are automatically synced daily.
- Test retrieval with ownership-related keywords, verifying that highly matching documents rank higher after
usingReRankis enabled. - Manually compare retrieval results against matching original documents, confirming that the
similaritythreshold setting meets business requirements.
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.