What this category's data looks like
This page addresses the scenarios of school safety hazard inspection and campus incident reporting. Material types include safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are updated weekly or monthly, with fields including inspection items, hazard description, inspector signature, and date; hazard rectification ledgers are updated by rectification batch, with fields including hazard name, rectification measures, responsible person, completion date, and acceptance signature; emergency incident reports are submitted immediately upon occurrence of the incident, with fields including incident name, occurrence time, number of people involved, handling process, and receipt. When these three types of materials enter the knowledge base retrieval and recall function, safety inspection checklists and hazard rectification ledgers serve as basis sources providing clauses and records, emergency incident reports serve as event fact sources providing process and receipt, and together the three support cross-material basis queries.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks and similarity scores (after mode, merge, re-rank, filter, and limit truncation). The basis entries that can be traced back to the original text are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Inspection items, hazard description, inspector signature, and date are complete, and the hazard name can be matched with that in the hazard rectification ledger | Retrieve the checklist entry in the search test, and check whether the returned candidate scores and original text chunks cover the inspection items and signature date |
| Hazard rectification ledger | Hazard name, rectification measures, responsible person, completion date, and acceptance signature are complete, and do not conflict with the dates in the safety inspection checklist | Switch searchMode to hybrid retrieval, and compare whether the name, quantity, and date of the same hazard are consistent between the ledger and the checklist |
| Emergency incident report | Incident name, occurrence time, number of people involved, handling process, and receipt are complete, and the version is current | Retrieve the report, check whether the candidate chunks contain the receipt and signature, and verify whether the date matches the same incident in the ledger |
| Knowledge base retrieval service | Candidate chunks and similarity scores are returned after mode, merge, re-rank, filter, and limit truncation | Adjust similarity and limit to observe changes in the number of candidates, and enable usingReRank to compare the ranking of the top few results |
Three common errors
- Symptom: The name of the same hazard does not match between the safety inspection checklist and the rectification ledger. Cause: naming was not unified when entered in the two places, and the original text was not checked after retrieval hit.
- Symptom: The date of the emergency incident report is inconsistent with the ledger record. Cause: versions were not synchronized, and the old version of the report is still in the knowledge base participating in recall.
- Symptom: The rectification ledger lacks an acceptance signature or the incident report lacks a receipt. Cause: material archiving is incomplete, but retrieval still returns that chunk.
How to verify the setup
This feature acceptance: test once each with synonym-rewritten questions, compare candidates and scores, then toggle re-ranking on and off to see the ranking of the top few results; record the number of candidates and scores, and adjust similarity, limit, searchMode, and usingReRank to observe differences.
Business test: ask a cross-material basis question and see whether the answer provides a traceable source.
- In the search test, retrieve the same basis question once with each of two phrasings, record the number of candidates and scores, and check whether both can hit the same original text chunk.
- Retrieve once with re-ranking enabled and once disabled, compare the order of the top few candidates, and confirm whether the relevant chunks are ranked at the front.