What the documents look like
Fresh-food weighing and sorting happens inside the warehouse fulfilment step, and the working data centres on weight and specification. A sorting task sheet records the order and the sorting requirement. A weighing label records the actual weighed result. A short-weight compensation form records a request to handle a weight difference. A quality inspection record records the quality decision. These materials update per order or per day.
For the contract and transaction material comparison task, the fields to reconcile include the specification requirement on the sorting task sheet, the actual weight on the weighing label, the difference quantity on the short-weight compensation form, and the decision result in the quality inspection record. These materials come from different steps, so the subject, the object and the status need to be aligned item by item. A status such as pending review is not a completed compensation, and a recorded difference does not by itself settle responsibility.
Constraints at the retrieval step
The knowledge base search node can link one or more knowledge bases that use the same vector model. Knowledge bases using different vector models cannot be linked together; the vector model identifier is checked first and non-matching bases are excluded. The search mode can be semantic retrieval, full-text retrieval or hybrid retrieval. Hybrid retrieval merges multiple result paths through RRF, which is an internal step of the retrieval chain. The minimum relevance value takes effect only in semantic retrieval or when result reranking is used, and it acts as a similarity filter rather than a permission or entity isolation control. The citation limit controls the length of cited content in tokens. Question optimisation performs coreference removal and question expansion and makes an additional model call. Image retrieval requires an image input and the corresponding model capability. Reranking requires a rerank model and must be enabled in the settings.
Hypothetical paper exercise sample: the material text to be checked reads "Sorting task sheet FD-2025-0412-017: order O-8841, specification requirement 500g±20g, sorter A, date 2025-04-12." "Weighing label W-2025-0412-017: actual weight 465g, weighing time 2025-04-12 09:15." "Short-weight compensation form C-2025-0412-009: order O-8841, declared difference 35g, status pending review, date 2025-04-12." The draft sentence to be assessed reads "Order O-8841 has completed the 35g short-weight compensation, and the sorting task is closed."
Configuration and implementation checks
The settings below relate to the contract and transaction material comparison task for the sample above. The values are starting points for this hypothetical exercise and need comparison against observed results before adjustment.
| Configuration item | Hypothetical starting point and reason | How to check |
|---|---|---|
| Linked knowledge bases | Select bases containing sorting task sheets, weighing labels, short-weight compensation forms and quality inspection records, and confirm the vector model identifiers match | Check the vector model identifier and exclude non-matching bases |
| Search mode | Start with hybrid retrieval to cover both semantic recall and identifier keyword hits | Test with the order number and the specification description from the sample |
| Citation limit | Set a token amount that can hold the complete fields of the three material types, so status fields are not truncated | Check whether the returned content includes the compensation form status and date |
| Minimum relevance | Label relevant and irrelevant samples first, then set an initial threshold; this value applies only in semantic retrieval or result reranking | Compare returned content before and after threshold adjustment |
| Question optimisation | Enable for queries containing references or omitted subjects, and compare the subject in the original and optimised question | Check whether the optimised question keeps the order number and date |
| Result reranking | Enable when candidate results are numerous and a rerank model is available, using the rerank score to assist filtering | Compare ordering before and after reranking and confirm status fields are retained |
Three common errors
- Treating the "pending review" status on the short-weight compensation form as a completed compensation. The input is the status field in the sample, the comparison is between the values "pending review" and "completed", and a draft sentence stating the compensation is completed does not match the source status. Pending review does not demonstrate that compensation was executed.
- Judging the 465g weighing label as failing the 500g±20g specification requirement without checking the tolerance. The input is the lower specification bound of 480g and the actual weight of 465g, the comparison is whether the actual weight falls inside the permitted range, and a conclusion reached without checking the tolerance lacks a basis. A difference being present does not settle responsibility.
- Treating retrieved material content as an authorisation to execute. The input is the compensation form content returned by retrieval, the comparison is between the retrieval result and the authorisation status, and treating a retrieval hit as permission to execute the compensation confuses retrieval with authorisation. Retrieval does not carry an authorisation function.
How to verify the setup
- Input the draft sentence from the sample, "Order O-8841 has completed the 35g short-weight compensation, and the sorting task is closed", and compare it against the status field "pending review" in the compensation form source. Observe whether the returned content includes the status field and whether the draft sentence matches the source status. If the returned content is missing the status field, check whether the citation limit truncated it.
- Input the order number O-8841 and the date 2025-04-12 from the sample, and compare whether the retrieval returns the sorting task sheet, the weighing label and the short-weight compensation form together. Observe whether the returned results cover materials for the same order and the same date. If only some materials are returned, check the linked knowledge base scope and the search mode.
- Input a query without an order number, such as "compensation form handling status", and compare the question before and after optimisation to see whether the subject is completed. Observe whether the optimised question retains checkable order or date information. If the optimised question loses the subject, record the observation and check the question optimisation settings. An empty result can be checked against the downstream design using the explicit paper input [], without asserting that a fictional rule retrieval always returns an empty array.