What this category's data looks like
This page addresses the vocational school student internship management scenario, and the materials include three types: internship agreements, internship plans, and internship logs. Internship agreements contain unit and school names, position, term, remuneration, signature, and receipt fields; internship plans contain week numbers, position rotation, mentoring arrangements, dates, and approval signatures; internship logs contain dates, task entries, work hours, mentoring comments, and signatures. Materials enter the knowledge base in batches; agreements and plans are updated with the semester or batch, while logs are submitted weekly or by stage. After entering this feature, agreements and plans serve as the anchor for terminology and field definitions, while logs serve as the instance and record role; together, the three provide candidate snippets and similarity scores for subsequent nodes to generate a unified terminology table and comparison draft.
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 upper-limit trimming). The "unified terminology table and comparison draft" is then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether the unit name, position name, term, remuneration, signature, and receipt fields are consistent with the internship plan | In the knowledge base search test, switch searchMode to semantic, full-text, or hybrid, and check whether the candidate snippets simultaneously cover the same field in both the agreement and the plan |
| Internship plan | Whether the week numbers, position rotation, mentoring arrangements, dates, and approval signatures correspond to the internship logs | Turn usingReRank on and off, compare the order of the first few candidates, and confirm that the dates in the plan and the dates in the logs can refer back to each other |
| Internship log | Whether the dates, task entries, work hours, mentoring comments, and signatures are consistent with the names, quantities, and dates in the agreement and plan | Check the number of returned candidates and the scores, record the array length separately, then verify whether the tokens budget of the quoted text after similarity filtering preserves the key snippets |
| Unified terminology table and comparison draft | Whether the same term is written consistently throughout and the translated name can refer back to the source text | Sample three terms to check whether their writing is consistent throughout, and after limit trimming confirm that key passages have not been truncated |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the agreement and the plan. Cause: the two materials' versions are not synchronized, the update batches differ, and retrieval candidates are mixed with old-version fields.
- Symptom: the log lacks a signature or receipt, and the plan's approval column is empty. Cause: the submission step is not closed-loop, fields are missing when the materials enter the knowledge base, and candidate snippets cannot refer back to the source text.
- Symptom: there are many candidates but the ones ranked first are all irrelevant, and the answer lacks key passages. Cause: the retrieval mode does not match the material form, rerank is not enabled, and similarity filtering and quoted upper-limit trimming are too tight.
How to verify the setup
This feature's acceptance: test once each with synonym-rewritten questions, compare candidates and scores, then toggle rerank on and off to inspect the ordering of the first few results; at the same time switch searchMode, adjust usingReRank and similarity, and record the number of candidates and scores.
Business test: sample three terms to check whether their writing is consistent throughout, confirm that the translated names can refer back to the source text, and that the date, quantity, and signature fields correspond to one another across the agreement, plan, and log.
- In the knowledge base search test, switch
searchModeto semantic, full-text, or hybrid, compare the candidate snippets and similarity scores for the same question, and confirm that the multi-path merged results include both semantic and full-text candidates. - Turn
usingReRankon and off to compare the ordering of the first few results, then verify the tokens budget of the quoted text aftersimilarityfiltering andlimittrimming, and record the array count separately.