What this category's data looks like
This page focuses on business basis queries in the scenario of signing research project task books. The materials include project task books, topic task breakdown tables, and budget books. The project task book is provided by the research management department at the signing stage, and its fields include project name, principal investigator, start and end dates, signature, and seal; the topic task breakdown table is prepared by the research group after the task is assigned, and its fields include topic number, task content, responsible person, and completion time; the budget book is submitted by finance or the project team during the application and signing stages, and its fields include subject name, amount, calculation basis, and approval signature. When these three types of materials enter this function, the project task book serves as the primary basis, the topic task breakdown table is used to check task boundaries and personnel division of labor, and the budget book is used to check funding subjects and amounts. In terms of update rhythm, there may be multiple revisions before signing; after signing, the current version prevails, and old versions are retained on file but are not used as the basis for answers. In terms of field characteristics, the same record may have inconsistent topic names, quantities, or dates in the task book and breakdown table, and the budget book subjects may also fail to match the funding column in the task book; missing signatures or receipts are common.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which determine 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 is controlled by a slider for 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 |
|---|---|---|
| Project task book | Fields include project name, principal investigator, start and end dates, signature and seal; check against the topic task breakdown table whether topic names, quantities, and dates are consistent | In application settings, check the response limit switch and slider position, ask a question requiring a long answer and see whether the ending is complete; use maxResponse to observe the length of a single answer |
| Topic task breakdown table | Fields include topic number, task content, responsible person, and completion time; check task boundaries and personnel division of labor against the project task book, and check subject correspondence against the budget book | Check maxContext and quoteMaxToken to confirm the range of context that can be accommodated and the budget for quoted content; the number of quotes is recorded separately according to array length |
| Budget book | Fields include subject name, amount, calculation basis, and approval signature; check subjects and amounts against the funding column in the project task book, and check whether signatures or receipts are complete | Compare usage between two runs to confirm changes in single-run usage after adjusting the limit; check whether the answer is cut off mid-sentence or clearly exceeds the needed length |
Three common errors
- Phenomenon: The same topic name is written differently in the task book and the breakdown table, and dates or quantities do not match. Cause: The two materials are filled in by different roles at different stages, and no field-level check was performed.
- Phenomenon: The budget book subjects and the amounts in the funding column of the task book are inconsistent, and the answer cites an old version. Cause: Versions were not synchronized, and the current version was not uniformly replaced after revision.
- Phenomenon: The task book lacks a signature or receipt, and the responsible person column in the breakdown table is blank. Cause: The signing process was not completed, and the materials entered the query scope in advance.
How to verify the setup
Acceptance of this function: ask a question requiring a long answer and see whether the ending is complete; check the response limit slider position and confirm that maxResponse matches the answer length required by the page.
Business test: ask a basis question spanning materials and see whether the answer gives a traceable source; check the number of quotes against the quoteMaxToken budget, record the array count separately, and do not perform an equality comparison.
- In application settings, check the response limit switch and slider position, compare usage between two runs, and confirm changes in single-run usage after adjusting the limit.
- Ask a question requiring a long answer and see whether the ending is complete, and check whether the answer is cut off mid-sentence or clearly exceeds the needed length.