What data for this category looks like
This category’s data primarily comes from the National Press and Publication Administration’s service platform, copyright registration systems, game package files, and operating institution filing materials. Commonly used documents include four types: declaration request files, game license application forms, copyright ownership certificates, and content review reports. Core fields include declaration subject name, game filing number, copyright registration number, review opinion document number, and others. The data update frequency is irregular per game declaration cycle. The document length of a single declaration material varies widely, ranging from hundreds to tens of thousands of characters.
What constraints do these characteristics impose on the reranking and hybrid retrieval link?
Documents for this category must strictly match official declaration requirements, with high standards for field accuracy. Hybrid retrieval must cover both keyword matching and semantic matching to ensure retrieval of key information such as declaration document numbers and game names. Data updates are irregular, so the latest version of declaration materials must be retrieved first to avoid using expired documents that affect approval accuracy. The document length of a single declaration material varies widely. The reranking link must adjust sorting weights for core fields, filter historical materials unrelated to the current declaration, and control the total length of retrieval results to avoid exceeding context window limits.
How to set configurations
| Configuration Item | Recommended Value Range | Rationale |
|---|---|---|
| Similarity threshold | 0.72–0.85 | Declaration materials for this category have strict field requirements. This range filters low-similarity irrelevant documents to avoid interfering with approval verification work |
| Single search upper limit | Top 8–12 results | The number of declaration materials per game is limited. Too many retrieved results will increase context processing burden and reduce retrieval efficiency |
| Retrieval mode | Hybrid retrieval | Must combine keyword matching and semantic matching to cover different types of retrieval fields such as declaration document numbers, game names, and copyright numbers |
| Enable reranking | Enabled | This category requires precise matching of core declaration fields. Reranking filters irrelevant materials and improves the sorting priority of key information |
| Reranking recall count | Top 3–5 results | The number of core declaration fields is limited. Only high-recall results need to be reranked to avoid redundant calculations |
| Field matching priority | Declaration document number, game name take priority | The core retrieval goal for this category is official declaration materials for a specific game. Prioritizing matching filing fields improves retrieval accuracy |
Three common errors
- Symptom: The reranking model can output normal sorting results during separate knowledge base testing, but in the pre-sales Q&A workflow bound to this process, the retrieval results do not show the reranked order, and the reranking status is marked as false. Cause: The reranking model was not bound in the exclusive configuration of this pre-sales Q&A workflow, and the reranking model configuration was only completed in the general knowledge base testing phase.
- Symptom: Only the reranking model appears in the channel model list, and other language models cannot be called. Cause: Model call permissions were not correctly configured during deployment, and the reranking model binding configuration overrode the call links of other language models.
- Symptom: Retrieval results include expired review reports or older version declaration materials. Cause: No retrieval constraint for filtering by update time was set, and hybrid retrieval did not prioritize retrieving the latest version of declaration documents.
How to confirm the configuration is complete
- Navigate to the corresponding pre-sales Q&A workflow configuration page in FastGPT v4.17.0, confirm that the "Enable Reranking" switch is turned on.
- Submit a test question targeting a specific game declaration, check whether the sorting of retrieval results is adjusted based on semantic relevance to the question, and whether results with core declaration fields are ranked at the top.
- Verify that the total number of retrieval results matches the configured "Single Search Upper Limit" value, with no redundant results exceeding the set quantity.
- Check the workflow running logs, confirm that there are call records for the reranking model and no error messages.
- Review the channel model list, confirm that both the reranking model and other language models can be selected, with no coverage restrictions.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.