What this category's data looks like
This page addresses the scenario of school safety hazard inspection and campus incident reporting. Materials come from three types of records: safety inspection checklists, hazard rectification ledgers, and emergency incident reports, as well as multilingual terminology explanations and receipts. Safety inspection checklists are updated weekly or per inspection, with fields including inspection item, location, responsible person, and date; hazard rectification ledgers are updated on a rolling basis by rectification round, with fields including hazard name, quantity, rectification deadline, acceptance inspector, and signature; emergency incident reports are submitted within a time limit after the incident occurs, with fields including incident name, time, number of people involved, reporter, and receipt. When the three types of materials enter knowledge base retrieval, they play different roles: checklists and ledgers serve as the reference draft for terminology and fields, incident reports serve as the source of back-reference for multilingual translated names, and receipts and signature pages are used to verify whether the name, quantity, and date of the same record match across the two materials, and whether the versions are synchronized.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate snippets and similarity scores (after pattern, merge, re-rank, filter, and limit trimming). The unified terminology table and reference draft are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Fields include inspection item, location, responsible person, and date; the name and quantity of the same record must be consistent with the ledger | In the knowledge base search test, switch searchMode, compare whether semantic and full-text candidates simultaneously cover the inspection item and location, and record the number of candidates and scores |
| Hazard rectification ledger | Fields include hazard name, quantity, rectification deadline, and acceptance signature; dates must match the checklist | Test once each with synonym-rewritten questions, turn usingReRank on and off to compare the ranking of the top few results, and check whether signatures and receipts are complete |
| Emergency incident report | Fields include incident name, time, number of people involved, reporter, and receipt; translated names can back-reference the original text | Adjust similarity and limit, observe the number and content completeness of returned references, and separately record the array length and reference text tokens |
| Multilingual terminology reference draft | The same term is consistent throughout the entire document, translated names can back-reference the original text, and the version is synchronized with the latest materials | Sample three terms to check whether their usage is consistent throughout the document, and verify whether the reference draft version number is synchronized with the ledger and reports |
Three common errors
- Phenomenon: The name, quantity, and date of the same hazard do not match between the checklist and the ledger. Cause: The two materials were entered separately, without terminology and field cross-referencing, and versions were not synchronized.
- Phenomenon: The incident report lacks a signature or receipt, and the reporter and acceptance inspector fields are empty. Cause: The material circulation step was not backfilled, and retrieval only obtained the body snippet.
- Phenomenon: There are many candidates but the top-ranked ones are irrelevant, and the answer lacks key paragraphs. Cause: The retrieval mode does not match the material form, re-ranking is not enabled, or similarity filtering is too loose.
How to verify the setup
Acceptance of this feature: Test once each with synonym-rewritten questions, compare candidates and scores, then turn re-ranking on and off to observe the ranking of the top few results; record the number of candidates and scores, and verify searchMode, similarity, limit, and usingReRank.
Business test: Sample three terms to check whether their usage is consistent throughout the document, verify whether translated names can back-reference the original text, and check whether signatures and receipts are complete.
- In the knowledge base search test, test the same question once with each different phrasing, record the number of candidates and scores, and compare whether semantic and full-text results appear simultaneously.
- Sample three terms to check whether their usage is consistent throughout the document, and verify whether the reference draft version matches the dates, quantities, and signatures of the checklist, ledger, and incident reports.