What this category's data looks like
This category's data involves three core types of materials: registration forms, care bonus-point materials, and admission rosters. Registration forms contain the candidate's name, ID number, application level, signature, and date; care bonus-point materials contain the bonus item name, point value, supporting document number, and reviewer signature; admission rosters contain the admitted major, planned number, admitted number, and person-in-charge signature. Materials enter the knowledge base in batches by registration season, review season, and admission season, with an update cadence synchronized with the enrollment process. When the three types of materials enter the knowledge base retrieval and recall function, each participates in indexing as an independent source: registration forms are used to verify identity and application information, bonus-point materials are used to verify care eligibility and point values, and admission rosters are used to verify admission results and plan execution. In terms of field characteristics, dates, names, quantities, and signatures are the key anchors for cross-material comparison, and version synchronization and receipt completeness directly affect source localization in exception tracing.
Configuration and implementation checks
The knowledge base retrieval service (retrieval node and search test) only outputs candidate snippets and similarity scores (after mode, merge, rerank, filter, and limit trimming); the exception list and review conclusions must be handled by subsequent nodes or manually. A single retrieval consists of question optimization, semantic/full-text/hybrid recall, multi-path merge, rerank secondary sorting, similarity filtering, and reference limit trimming, and only then is the reference content handed to the model.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Whether the name, ID number, and date of the same candidate are consistent between the registration form and the bonus-point materials; whether the signature and receipt are complete | In the knowledge base search test, use synonymous questions to retrieve the same candidate, compare candidate snippets and similarity scores, and check the fields of the two materials |
| Care bonus-point materials | Whether the bonus item name, point value, and supporting document number are consistent across the registration form and admission roster; whether the reviewer signature exists | Switch retrieval modes, observe whether semantic and full-text candidates hit both the bonus-point materials and the registration form, and record the number of candidates and scores |
| Admission roster | Whether the admitted major, planned number, and admitted number match between the roster and the registration form; whether the person-in-charge signature and version date are synchronized | Compare the order of the top few items before and after enabling rerank, check the tokens and array length of the reference text, and record the number of references separately |
| Knowledge base retrieval service | Whether candidate snippets and similarity scores are returned after mode, merge, rerank, filter, and limit trimming | In the search test, adjust searchMode, usingReRank, similarity, and limit, and verify the candidate and reference content |
Three common errors
- Symptom: the name or date of the same candidate does not match between the registration form and the bonus-point materials. Cause: the two materials were entered at different times, versions were not synchronized, and cross-material field comparison was not performed when retrieval hit.
- Symptom: the planned number in the admission roster is inconsistent with the application number in the registration form. Cause: the roster update lags, the old version is still recalled, and candidate snippets are not labeled with a version date.
- Symptom: the bonus-point materials lack a reviewer signature or receipt. Cause: the scanned materials are incomplete, the reference content returned by retrieval does not cover the signature area, and it cannot be confirmed during review.
How to verify the setup
Acceptance of this function: test once each with synonym-rewritten questions, compare candidate snippets and similarity scores, then toggle rerank on and off to observe the ordering of the top few items; check the impact of searchMode, usingReRank, similarity, and limit on the number of candidates and scores, and record the number of references separately by array length.
Business test: create an exception record and see whether the source material can be traced.
- In the knowledge base search test, use different phrasings for the same candidate to retrieve the registration form and bonus-point materials, record the number of candidates and similarity scores, and check the name, date, and signature fields.
- For the admission roster, compare the order of the top few items before and after enabling rerank, check the tokens and array length of the reference text, and confirm whether the version date and person-in-charge signature are synchronized.