What This Category of Data Includes
Data for this category comes from four core sources: special equipment safety supervision systems, inspection and testing institution systems, user unit ledgers, and operator certificate databases. The update frequency is monthly. Daily processed documents include use registration certificates, periodic inspection reports, maintenance records, hidden danger rectification notices, accident reports, and operator certificates. Core fields include unique device identification numbers, inspection validity periods, operator certificate numbers, hidden danger rectification statuses, and others. Individual document structures are fixed, but document types vary widely. The data covers supervision information across the full lifecycle of special equipment.
Constraints for Knowledge Base Retrieval and Recall
The monthly update frequency requires the knowledge base to run full synchronization tasks regularly. This prevents data lag that impacts review accuracy. Differences across multiple document types require retrieval logic to balance precise field matching and semantic content association. This avoids missing key review information. Core review steps rely on precise fields such as device numbers and inspection cycles. Retrieved results must have high matching accuracy. This prevents irrelevant documents from interfering with the review process. Serious consequences follow supervision errors. The recall range for retrieval results must be strictly limited to special equipment exclusive data. Regulatory information from other categories is not included.
Configuration Settings
The following configurations are designed for the knowledge base feature in FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | High accuracy is required for special equipment data. This range filters low-matching results and avoids incorrect associations between devices and irrelevant documents |
limit | Top 8 | Declaration material review requires covering all lifecycle-related documents for a device. Too many results increase review burden. Too few results may miss relevant materials |
searchMode | keyword + semantic | Both precise fields such as device numbers and semantic content such as maintenance records must be matched. This adapts to structural differences across multiple document types |
usingReRank | Enabled | Special equipment data has strong relevance. Reranking improves the sorting priority of high-matching results, reducing the risk of missing hidden danger checks |
datasetSearchUsingExtensionQuery | Disabled | Declaration material review requires strict matching of submitted material names and fields. Extended queries may introduce irrelevant content |
collectionIds | Specify the exclusive dataset ID for special equipment supervision | The retrieval range is limited to this category of data only. Documents from other regulatory categories are prevented from being included |
Three Common Configuration Errors
- Symptom: Retrieval results return non-special equipment regulatory documents. Cause:
collectionIdsis not configured to limit the exclusive dataset, leading to recall of cross-category data. - Symptom: A generic response is returned directly when no knowledge base matches are found, and no custom prompt is triggered. Cause: Retrieval trigger logic is not set correctly, or fallback content for no results is not configured.
- Symptom: Task fails when creating a plain text collection via the knowledge base interface, because an invalid value is passed for the
trainingTypeparameter. Cause: The range of valid options is not clarified, and an undefined parameter value is used.
How to Verify Correct Configuration
- Upload one special equipment use registration certificate and one unrelated administrative document. Run a retrieval query related to a device identification number. Confirm that only special equipment-related results are returned. Verify that the
collectionIdsconfiguration is active. - Enter a query that includes a device identification number and inspection validity period. Check the sorting of returned results. Confirm that high-matching documents are displayed first. Verify that the
usingReRankconfiguration is active. - Trigger a query with no matching results. Confirm that preset custom prompt content is returned. Verify that the no-result fallback logic works correctly.
- Call the knowledge base file detail export interface. Confirm that returned fields include special equipment exclusive information such as device identification numbers and inspection cycles. Verify that export configurations are correct.
The values provided here are common starting points. They 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.