What this category's data looks like
This page addresses multilingual materials and terminology processing for National Key R&D Program project applications. The materials include three types: the project application form, the budget application form, and the cooperation agreement. The project application form and the budget application form provide the research content, participating units, and funding basis, while the cooperation agreement provides the rights and responsibilities of each party and signing information. After these three types of materials enter dialogue and retrieval, they respectively take on the roles of terminology source, budget basis verification, and legal entity confirmation. The update rhythm advances with the application stages, and the field characteristics are concentrated in project name, participating units, funding amount, start and end dates, signatures, and receipts. Multilingual materials also need to be checked against translated names, with the same term identified back and forth between the source text and the translation. When materials enter this function, the server-side model channel configuration first completes model binding, and then dialogue and retrieval use that model to produce a unified terminology list and comparison draft.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting the model binding relationship and channel response. The unified terminology list and comparison draft are then completed by subsequent AI nodes, code nodes, or manual work. Models are divided into five categories: language, indexing, reranking, speech synthesis, and speech recognition. Different stages bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Project application form | The project name, participating units, and start and end dates must match the budget application form and cooperation agreement item by item | Compare the corresponding fields of the three materials, and check whether the name, quantity, and date are from the same source and same version |
| Budget application form | The funding amount and budget subjects must be consistent with the basis of the project application form, and dates and signatures must not be missing | Check the values and dates in the budget table and the main text of the application form, and check whether signatures and receipts are complete |
| Cooperation agreement | The partner names, task division, and signing date must be consistent with the application materials | Check the signature page of the agreement and the list of participating units in the application form, and confirm that the versions are synchronized |
| Model configuration | The model type corresponds to the stage in which it is to be used, and the model identifier is consistent with the name listed in the documentation | In the model configuration, check the type label, compare it with the model name returned by the channel, and check the value basis of maxContext, maxTokens, and quoteMaxToken |
Three common errors
- Symptom: The same project name is written differently in the application form and the budget form. Cause: The two materials are maintained separately, versions are not synchronized, and there is no unified terminology list referring back to the source text.
- Symptom: The funding amount or start and end dates do not match between the two materials. Cause: After a budget adjustment, only one place was changed, while the other still uses the old record, and no item-by-item comparison was made.
- Symptom: The cooperation agreement lacks a signature or receipt, but the application materials have already been submitted. Cause: The signing process and the application process run in parallel, receipts were not archived, and the completeness check of materials is missing.
How to verify the setup
This function's acceptance: run one dialogue and one retrieval, check the model identifier in the response, confirm that the binding relationship between the language model and the indexing model is correct, and check the value of toolChoice.
Business test: sample three terms and check whether their spelling is consistent throughout the entire text, confirm that translated names can refer back to the source text, and record the cited text tokens and the number of array items separately.
- In the model configuration, check item by item the model type labels and the names listed in the documentation, and confirm that the channel and key source are consistent with the accessed service.
- Place the same record fields from the project application form, budget application form, and cooperation agreement side by side for comparison, and check whether names, quantities, dates, signatures, and receipts are complete.