Declaration Material and File Review for Land Use Rights, Mining Rights, and State-Owned Property Transactions: Citation Sources and Traceability

What this category of data looks like

Daily documents for this category include transfer announcements, transaction notices, bid applications, margin payment vouchers, transaction confirmation letters, listing result announcements, and property right transfer descriptions. Data sources are the national public resource trading platform, natural resource trading systems, property right exchange systems, and state-owned asset supervision systems, with an update frequency of once per day. Document fields typically include transaction object ownership number, object type, margin amount, transaction confirmation time, transfer base price, and other relevant items. Some documents include ownership certificate attachments. The data structure primarily mixes structured fields and unstructured text.

Constraints for citation sources and traceability

The daily updated data requires the citation and traceability process to ensure real-time synchronization and verification of data sources, and prevent use of expired ownership or transaction information. Mixed access to multi-source data requires clear classification rules for documents from different systems, to ensure that retrieved documents such as transfer announcements and transaction confirmation letters match the declaration materials under review. Documents contain both structured fields and unstructured text, so retrieval and matching logic must be configured appropriately. This ensures accurate traceability for key fields such as ownership numbers and margin amounts, and avoids review disputes caused by inconsistent data sources.

Configuration settings

Reference only; verify against the target FastGPT release and deployment documentation.

Three common misconfigurations

• When configuring responseData, failing to filter tool call logs, resulting in redundant knowledge base search input and response content appearing in the output. This happens because the requirement to return only audit-required document fields is not clearly defined, and display of irrelevant tool logs is not disabled.
• Setting too small a value for quoteMaxToken, leading to truncation of long documents such as transaction confirmation letters and property right transfer descriptions, and loss of key ownership information. This happens because the average text length of core documents for this category is not matched.
• Not enabling the detail configuration item, preventing the traceability link from displaying document source systems and update times, making it impossible to verify data timeliness and compliance. This happens because the business requirement for clear traceability basis in this category of audits is overlooked.

How to verify correct configuration

Reference only; verify against the target FastGPT release and deployment documentation.

• Upload a transaction confirmation letter document from this category, trigger an audit query, and check whether the output only includes core audit fields such as transaction object and margin amount.
• View the traceability information in the output, confirm whether the document source system and update time are displayed, to verify that the detail configuration is active.
• Adjust the value of quoteMaxToken, test whether documents of different lengths can fully retrieve key information, and confirm that the value matches the average length of documents in this category.
• Test multi-data source access scenarios, check whether documents from corresponding systems can be correctly retrieved, to verify that the configured data source association rules are effective.

The values provided here 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.