What the documents look like
JD POP third-party store operations work with four main record types: product information tables, dispatch timeliness agreements, dispute handling forms, and warranty-period service records. The public brief describes updates at daily frequency and per order. In operating reviews and exception reviews, staff align dispatch times, buyer addresses, and dispute evidence materials to specific records. These four record types use different field conventions, so any comparison must hold the same subject, the same period, and the same field.
A product information table records product identifiers and attributes. A dispatch timeliness agreement records a promised time limit. A dispute handling form records the disputed object and its current status. A warranty-period service record records service scope and validity period. Retrieval does not verify any of these values, and a retrieved record is not an authorization decision.
Constraints at the retrieval step
The knowledge base search node can associate one or more knowledge bases that use the same vector model. Knowledge bases using different vector models cannot be associated together. The node outputs cited content as an array, and the array length can be zero, which means the output path still completes when no content is found.
Semantic retrieval suits natural-language questions. Full-text retrieval suits exact queries such as identifiers, model numbers, and proper nouns. Hybrid retrieval uses both and merges results through RRF, after which ReRank can reorder candidates. The minimum relevance value takes effect only in semantic retrieval or when result reranking is used. The citation limit is measured in tokens. Problem optimization performs reference resolution and question expansion before retrieval, and it adds a model call.
Hypothetical paper exercise: a JD POP store operator reviews one dispute during an exception review. The materials available for comparison read: "Dispute handling form JD-2024-0312 records that the buyer claims delayed dispatch; the store submitted a dispatch time screenshot as evidence; the current status is pending platform review. The dispatch timeliness agreement states the product is promised to ship within 48 hours. The warranty-period service record shows the order warranty period is 30 days after signing." The draft sentence to be assessed reads: "The dispute has been determined to be the store's responsibility, and the warranty-period service record can serve as direct evidence of delayed dispatch."
Configuration and implementation checks
The table below lists documented settings or implementation checks relevant to this page and this task. The hypothetical starting values apply only to this paper comparison and are not official defaults.
| Configuration item | Hypothetical starting value for this exercise | Reason and comparison method |
|---|---|---|
| Associated knowledge bases | Associate only the dispute handling form base that uses the same vector model | Check the base identifier and vector model identifier, and exclude bases whose model differs |
| Search mode | Hybrid retrieval | Recall both the identifier "JD-2024-0312" and the natural-language question, then compare with semantic retrieval alone |
| Citation limit | Hypothetical starting value of 2000 tokens | Test whether long and short dispute forms are returned in full, and compare with truncation at a smaller limit |
| Minimum relevance | Hypothetical starting value of 0.4 | Label relevant and irrelevant passages in the sample first, then compare filtering results at 0.3 and 0.5 |
| Problem optimization | Enabled for multi-turn follow-up questions | Compare the original question with the optimized question and check whether the subject was changed incorrectly |
| Result reranking | ReRank enabled | Reorder hybrid retrieval candidates when many are returned, and compare with the ordering before reranking |
Three common errors
- Treating a retrieved record as an authorization conclusion. In the sample, the dispute handling form status is pending platform review. Retrieving that form shows the record exists. A check inputs the form text, compares the value "pending platform review" with the phrase "responsibility determined," and observes whether the draft sentence turns a pending status into a determined one.
- Treating the warranty-period service record as direct evidence of delayed dispatch. That record covers a 30-day service scope after signing, which is a different field from dispatch time. A check inputs both record texts, compares field subject and period, and observes whether a cross-field citation appears.
- Associating knowledge bases that use different vector models. A check inputs the vector model identifiers of the bases to be associated, compares whether the identifiers match, excludes those that do not, and records the actual observation. It does not run a cross-model retrieval to compare missed recalls.
How to verify the setup
- For the sample draft sentence, input the dispute handling form text and the warranty-period service record text. Compare the status "pending platform review" with the phrase "responsibility determined." Observe whether the draft sentence presents a pending status as determined. The expected phenomenon is that the draft sentence does not match the source status.
- For the identifier "JD-2024-0312" in the sample, input that identifier as the retrieval term. Compare the content recalled by hybrid retrieval with the content recalled by semantic retrieval alone. Observe whether the identifier is matched exactly. The expected phenomenon is that the hybrid retrieval result contains the form corresponding to that identifier.
- For empty-result handling, input an explicit paper input of []. Check whether the downstream design treats the cited content as an array of length zero. The expected phenomenon is that the output path completes and the citation array is empty.
These checks describe comparisons and expected observations. They do not record a completed test, an approval, or a deployment. Where a record field is not provided, the value remains unknown.