What this category's data looks like
Kindergarten home-school co-education communication materials, with sources including the kindergarten's own commitments and response times, child performance observation records, parent demand categories, notification delivery receipts, and class communication ledgers. The update cadence is weekly or event-triggered, and new records enter the knowledge base after being archived. When materials enter the knowledge base retrieval service, commitments and response times serve as the draft for checking response timeliness, child performance descriptions serve as the original text for comparison with observation records, parent demand categories serve as the reference for classified feedback, and notification delivery records serve as the basis for confirming reach. The retrieval service is only responsible for recall and scoring, not for determining whether materials are current, whether they belong to this kindergarten, or whether they match the original text.
Configuration and implementation checks
The knowledge base retrieval service (retrieval node and search test) only outputs candidate snippets and similarity scores (after pattern, merge, rerank, filter, and limit trimming); the basis entries that can be traced back to the original text must be handled by subsequent nodes or manually. A single retrieval consists of question optimization, semantic/full-text/hybrid recall, multi-path merging, rerank secondary sorting, similarity filtering, and citation limit trimming, and only then is the cited content handed to the model.
| Object | Check | Verification action |
|---|---|---|
| Commitments and response times | The entry can be traced back to the original text of this kindergarten's current commitments, and the response time is consistent with the record | In the search test, test once each with synonymous questions, switch searchMode to compare the number of candidate entries and scores, and check whether the returned snippets contain the original commitment text and response time |
| Child performance descriptions | The wording matches the observation records, and no summaries conflicting with the records appear | Initiate retrieval using keywords from the observation records, compare the order of the top few entries before and after enabling usingReRank, and confirm that candidates come from this kindergarten's records, not from other materials |
| Parent demand categories | Feedback has been categorized, and the demand types match the handling records | Search by demand type terms, check whether the returned candidates cover the category field and handling records, and record the number of candidate entries and scores |
| Notification delivery records | The delivery status is consistent with the receipt, and unresponded items are verifiable | Search using the notification title and delivery status terms, check whether the returned snippets contain the original receipt text, and adjust similarity to observe changes in candidates |
Three common errors
- Phenomenon: a commitment was not responded to, yet no basis can be found. Cause: the commitment entry is not linked to the response record, retrieval only recalls one-sided snippets, and the association relationship must be manually supplemented.
- Phenomenon: child performance descriptions do not match the observation records. Cause: generalized wording entered the knowledge base first, the original snippets were not recalled, and comparison must be made item by item against the observation records.
- Phenomenon: parent demands are not categorized, and feedback is scattered. Cause: the demand category field is missing or not updated with the records, retrieval candidates cannot reflect the categorization, and categorization must be manually supplemented.
How to verify the setup
This feature's acceptance: test once each with synonymously rewritten questions, compare candidates and scores, then toggle rerank to inspect the ordering of the top few entries; switch searchMode and adjust similarity, record the number of candidate entries and scores, and check the tokens of the cited text after limit trimming.
Business test: ask a basis question that spans materials, and see whether the answer provides a traceable source.
- In the knowledge base search test, test once each with synonymous questions, compare the number of candidate entries and scores, and switch
searchModeto observe recall differences. - Run once each with
usingReRankenabled and disabled, compare the ordering of the top few entries, and check the tokens and array length of the cited text afterlimittrimming.