What the data for this category looks like
Data related to service consultation at state-owned capital operation companies comes from four main sources: publicly released state-owned assets supervision documents, internal group service guidelines, service-related submission materials from subsidiaries, and policy interpretation compilations. Update cycles vary across sources. State-owned assets policy documents are updated as needed to align with regulatory requirements. Internal service processes are adjusted quarterly. Service-related data from subsidiaries is updated monthly. Individual documents typically include standard fields: document number, issuing entity, applicable matters, handling steps, required materials, time limit for completion, accepting department, and consultation channels. Time limits for completion are measured in working days. Consultation channels include landline phones and online portals.
Constraints imposed on knowledge base retrieval and recall
Four key constraints arise from these data characteristics: First, data sources include both public and internal confidential content. Permission filtering rules must be configured based on user roles during retrieval. Only documents within the user’s assigned permission scope may be returned to prevent sensitive information leaks. Second, update cycles differ significantly across data types. Differentiated incremental synchronization cycles must be set for policy documents and internal process documents. This avoids recalling outdated service guideline content. Third, documents contain structured fields such as document number and time limit for completion. Support must be provided for exact field matching and combined retrieval. This improves the accuracy of service consultation responses. Fourth, individual service guideline documents are lengthy. Chunk length must be controlled appropriately. This prevents context fragmentation from reducing recall relevance.
Configuration settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
similarity | 0.75–0.85 | Service consultation requires balancing relevance and coverage. This range filters low-relevance results while retaining sufficient candidate entries |
limit | Top 8 entries | The number of service items for state-owned capital operation companies is moderate. 8 entries can cover relevant documents for common consultation scenarios |
searchMode | vector+keyword | Combines semantic retrieval and keyword matching. This can recall both structured fields and semantically relevant service documents |
usingReRank | Enabled | Performs reranking on long document chunk results. This improves the relevance of final recall results |
datasetSearchUsingExtensionQuery | Enabled | Optimizes user consultation questions through expansion. Adds service-related synonyms and limiting terms. For example, expand "property right transfer" to "state-owned asset property right transfer" |
collectionIds | Configured by service item grouping | Configures retrieval scope separately for different service process collections. This avoids cross-category interference |
Three common configuration errors
- Phenomenon: Only 1 result is returned after retrieval, failing to cover the complete consultation needs of the requesting party. Cause: The
limitparameter is set too low, failing to match the coverage scope of service items for state-owned capital operation companies. - Phenomenon: The interface returns a 504 gateway timeout status code. Retrieval response time exceeds a reasonable range. Cause: The
collectionIdsconfiguration includes too many irrelevant document collections. This leads to an overly large retrieval scope and increased computational load. - Phenomenon: Process screenshots attached to service guidelines fail to display properly in question-and-answer results, and the corresponding fields are empty. Cause: Knowledge base file access permissions are not configured correctly, or image files were not uploaded in a format supported by FastGPT.
How to verify successful configuration
- Submit a typical service consultation question, such as "What is the handling process for state-owned property right transfer". Check whether the relevance of returned results meets business expectations. Adjust the
similarityparameter to an appropriate range. - View FastGPT retrieval logs. Confirm that the number of recall results matches the
limitparameter setting, with no abnormal filtering. - Test consultation requests from users with different roles. Confirm that only service documents within the assigned permission scope are accessible to each requesting party, with no unauthorized recall.
- Upload a service process screenshot to the corresponding knowledge base collection. Submit a consultation containing keywords related to that process. Confirm that the screenshot displays properly in the question-and-answer results.
Note: The configuration values provided are common starting points. They should be evaluated against samples from the target deployment environment.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-28.