What this category's data looks like
This page addresses the scenario of school safety hazard inspections and campus incident reporting. Materials include safety inspection checklists, hazard rectification ledgers, emergency incident reports, as well as signable material drafts and handover records. Safety inspection checklists are updated periodically and contain inspection items, locations, dates, and inspector signatures; hazard rectification ledgers are updated on a rolling basis by entry and contain hazard names, quantities, rectification deadlines, responsible person signatures, and receipts; emergency incident reports are drafted immediately upon occurrence and contain incident names, involved quantities, dates, reporters, and recipients. When materials enter the knowledge base retrieval service, each serves as a source of candidate snippets: safety inspection checklists provide inspection item and signature fields, hazard rectification ledgers provide rectification status and deadline fields, and emergency incident reports provide incident description and reporting fields. The retrieval service only returns candidate snippets and similarity scores; drafts and handover records are generated by subsequent nodes or manually based on these.
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, rerank, filter, and limit trimming). Signable material drafts and handover records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Fields are complete, responsible person is clear, version and date are consistent; inspection items, locations, dates, and inspector signatures match | In the knowledge base search test, switch searchMode to semantic, full-text, or hybrid, and compare the number of candidates and scores; check whether the returned snippets contain inspection items, locations, dates, and signature fields |
| Hazard rectification ledger | Fields are complete, responsible person is clear, version and date are consistent; hazard names, quantities, rectification deadlines, and receipts match | Test once each with synonymous rewritten questions to see whether candidates include both semantic and full-text results; check whether hazard names, quantities, dates, and signatures in the returned snippets are consistent, and record the number of candidates and scores |
| Emergency incident report | Fields are complete, responsible person is clear, version and date are consistent; incident names, involved quantities, dates, and recipients match | Turn usingReRank on and off to compare the ranking of the top few results; check the number of returned citations and citation text tokens, and whether key snippets of incident names, quantities, dates, and recipients are still retained after similarity filtering |
| Knowledge base retrieval service | Candidates come from different recall channels and have been merged, the top few results are more relevant after reranking, and key snippets of the original text are still retained after filtering and limit trimming | In the search test, check whether the returned candidates include both semantic and full-text results; adjust limit to observe changes in the number of candidates, and separately record the length of the citation array and citation text tokens |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match across two materials. Cause: Candidate snippets come from different sources and enter the drafting step without item-by-item field verification.
- Symptom: The versions of the safety inspection checklist and hazard rectification ledger are not synchronized, and signatures or receipts are missing. Cause: After materials are updated, retrieval is not re-run, and old candidate snippets are still cited.
- Symptom: The same issue cannot be recalled when phrased differently, and although there are many candidates, the top-ranked ones are all irrelevant. Cause: The retrieval mode does not match the material form, reranking is not enabled, or similarity filtering is too broad.
How to verify the setup
Acceptance of this feature: Test once each with synonymous rewritten questions, compare the number of candidates and scores, then turn usingReRank on and off to see the ranking of the top few results; switch searchMode to compare semantic, full-text, and hybrid results, and separately record citation text tokens and array counts after similarity filtering and limit trimming.
Business test: Draft one according to the template and complete one handover to see whether missing items are blocked.
- In the knowledge base search test, switch
searchMode, test the same field once each with different phrasings, and record the number of candidates and scores. - Turn
usingReRankon and off to compare the ranking of the top few results, check the number of returned citations and citation text tokens, and confirm that key fields have not been lost due to trimming.