What this category's data looks like
This page is for the enterprise independent skilled talent evaluation scenario. The core materials include the enterprise evaluation filing form, evaluation specifications, and candidate roster. The filing form states the evaluation entity, occupational direction, and filing date; the evaluation specifications define the assessment modules, weights, and pass criteria; the roster records candidate identity, declared level, and batch. The three types of materials are updated synchronously by batch, and their fields are characterized by names, quantities, dates, and signatures. When entering the business basis query function, the filing form and evaluation specifications serve as the basis sources, while the roster serves as the basis for personnel scope and batch correspondence. Each plays a different role and together supports the generation of basis items that can be traced back to the original text.
Configuration and implementation checks
This part is executed by the application settings (response limit, etc.), which output the length of a single answer and the range of context that can be accommodated. "Basis items that can be traced back to the original text" are then completed by the model. The response limit uses a slider to control the length of a single answer. If set too low, the answer will be truncated; if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | Corresponds item by item with the occupational direction, evaluation level, and filing date in the evaluation specifications, and signatures and receipts are complete | Check whether the filing form fields are consistent with the evaluation specification items, and check whether signatures and receipts are missing |
| Evaluation specifications | Match each other with the declared level, assessment modules, and batch date in the candidate roster | Compare the names, quantities, and dates in the evaluation specifications and the roster, and confirm that the version is currently valid |
| Candidate roster | Personnel names, declared levels, and batch quantities match the filing form and evaluation specifications | Check item by item the names, quantities, and dates in the roster against the other two materials, and record any inconsistencies |
| Response limit | Matches the answer length required by the page; maxResponse controls the length of a single answer, and maxContext determines the range of context that can be accommodated | Check the switch and slider position in the application settings, and confirm the quoteMaxToken quote budget and the maxResponse limit |
Three common errors
- Phenomenon: The name, quantity, or date of the same record does not match between the filing form and the roster. Cause: The two materials are maintained at different paces, and cross-checking was not performed during entry.
- Phenomenon: The evaluation specification version is not synchronized, and old items are still referenced. Cause: The current version was not replaced after updating, and version identifiers between materials are missing.
- Phenomenon: The filing form lacks a signature or receipt, and the basis items cannot be traced back to the original text. Cause: The circulation step was not completed with sign-off, and material archiving is incomplete.
How to verify the setup
Acceptance of this function: ask a question that requires a long answer, see whether the ending is complete, confirm that the response limit matches the answer length, and check the maxResponse and maxContext settings.
Business test: ask a basis question that spans materials, see whether the answer gives a traceable source, and check the quoteMaxToken quote budget and the number of quoted items separately.
- In the application settings, check the response limit switch and slider position, and confirm that they match the answer length required by the page.
- Compare the usage of two runs, check the change in single-run usage after adjusting the limit, and check the quoted text tokens and array item count.