What This Category of Data Looks Like
Investment research data mainly comes from consolidated financial statements, individual subsidiary operating reports, industry regulatory documents, cross-segment business collaboration ledgers, and public research reports. Update frequency varies significantly by document type. Consolidated statements are updated quarterly. Individual subsidiary reports are synced with monthly operating data. Industry research reports and regulatory documents are updated irregularly alongside policy releases. Most documents have long text structures, and include fields such as consolidated revenue proportion, related transaction amount, and subsidiary business proportion. Units are primarily ten thousand yuan and hundred million yuan. Some documents include custom metadata fields such as subsidiary affiliated segment and report issuance date.
Constraints for Citation Source and Traceability
Decentralized data sources require traceability systems to cover metadata identification across multiple document types. Avoid displaying only content from a single subsidiary or segment. Different update frequencies create large timeliness gaps between some documents. Traceability processes must link document update time fields to ensure cited content remains timely. Long text structures and multi-field attributes require retaining field association relationships during segment processing. Splitting that breaks business logic and reduces content accuracy during traceability. Cross-entity associated data requires traceability annotations to link parent company and subsidiary information simultaneously. This improves content credibility.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
Recall Count | Top 8-12 entries | Cover investment research data across multiple business segments, avoid missing cross-subsidiary associated content |
Similarity Threshold | 0.72-0.85 | Balance recall precision and coverage for specialized documents, avoid irrelevant content being included or core data being missed |
Segment Length | 1000-1500 characters | Retain complete business logic for consolidated financial statements and related transaction documents, avoid splitting that breaks field associations |
Reranked Return Count | Top 4-6 entries | Prioritize displaying core segment data most relevant to the query, reduce information redundancy during traceability |
enable_citation | Enabled | Ensure conversation results display complete metadata for citation sources |
return_source_id | Enabled | Ensure conversation API returns knowledge base ID and document identifiers, meet traceability troubleshooting needs |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Phenomenon: In non-tool call mode, conversation response results do not include citation annotations for web search sources. Cause: The
enable_web_search_citationparameter is not enabled, or the traceability binding rule between search results and knowledge base content is not configured. - Phenomenon: The citation list returned in conversation responses only displays document titles, and does not label subsidiary names or business segments. Cause: The custom metadata extraction configuration is not enabled, and fields such as subsidiary affiliation and report type in the document are not extracted for traceability display.
- Phenomenon: When calling the conversation interface, the
sourcefield in the returned result is empty or does not include the knowledge base ID. Cause: Thereturn_source_idparameter is not enabled, or in version 3.9.2 and earlier, the return field range is not configured to include the knowledge base ID.
How to Verify Proper Configuration
- Upload a consolidated financial statement and an individual subsidiary operating report, submit a query related to related transaction content. Check whether the citation list in the returned result includes metadata for both types of documents.
- Enable non-tool call mode and web search, submit a cross-industry and cross-entity query. Check whether the returned result includes annotations for web search sources.
- Call the conversation interface, check whether the
sourcefield in the returned result includes the knowledge base ID, document title, and custom metadata fields. - Adjust the
similarity thresholdparameter to conduct a test. Check whether the number and relevance of recalled documents meet business requirements.
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-14.