What this category's data looks like
Materials for school safety hazard inspections and campus incident reporting typically include three categories: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists record inspection items, locations, dates, and inspector signatures; hazard rectification ledgers record hazard names, quantities, rectification deadlines, responsible person signatures, and receipts; emergency incident reports record incident names, number of people involved, occurrence dates, reporters, and receipt acknowledgments. Material sources are mostly internal campus patrols, superior-issued documents, and historical archives, with update cadence advancing along with inspection batches, rectification cycles, and incident handling. After the three material categories enter the retrieval scope, the node outputs only a cited content array, each entry containing an original text snippet and a source identifier, and the length can be 0; field comparison, ledgers, and reports are completed by subsequent AI nodes, code nodes, or manual work.
Configuration and implementation checks
The citation output of the knowledge base retrieval node outputs only a cited content array, each entry containing an original text snippet and a source identifier, and the length can be 0. Version ledgers and change records must be handled subsequently by AI nodes, code nodes, or manual work. Even if no content is found, the output pipeline still runs through.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Whether inspection items, locations, dates, and inspector signatures are complete, and whether the name and date of the same record match across two materials | Open the citation marker and verify fields and signatures against the source document; view quoteList and responseData (non-streaming module results returned with detailed output enabled) in the conversation to confirm the citation points back to the original paragraph |
| Hazard rectification ledger | Whether hazard names, quantities, rectification deadlines, responsible persons, and receipts are consistent, whether the old version is traceable, and whether citations are synchronized | Run a test with a question that has no matching material, and see whether the citation array is empty while the pipeline continues; record the array length and separately check the quoteMaxToken budget |
| Emergency incident report | Whether incident names, number of people involved, occurrence dates, reporters, and receipt acknowledgments are complete, and whether the version number and citations are updated in sync | After changing one piece of content, re-run retrieval and check whether the version number and citations are synchronized; compare against the source identifier to confirm the cited snippet matches the original text |
| Knowledge base associated collections | Whether the selected knowledge bases use the same vector model, and whether the search parameters match the values in the knowledge base retrieval section | Check the selected collections and vector model in the node; open the search parameter panel and verify each item |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the safety inspection checklist and the hazard rectification ledger. Cause: The two materials are maintained separately, without verification and synchronization under the same field definitions.
- Symptom: The cited snippet does not match the original text, or there is no citation marker in the answer. Cause: First check whether this round hit anything and which material was hit, then look at trimming; do not directly attribute it to length trimming.
- Symptom: The emergency incident report lacks signatures or receipts, and the old version cannot be traced. Cause: The version was not synchronized, citations were not updated with the materials, and change records were not made for the ledger and report.
How to verify the setup
Acceptance for this feature: ask a question with original-text evidence and check whether the citation array and markers point back to the original text; then ask a question with no matching material and confirm the array is empty while the pipeline runs through.
Business test: change one piece of content and see whether the version number and citations are updated in sync.
- In the node, check the selected knowledge base collections and their vector models, and open the search parameter panel to verify each value.
- Run a test with a question that has no matching material, record the citation array length, separately check the
quoteMaxTokenbudget, and confirm the pipeline continues when the array is empty.