What this category’s data looks like
The market and yield data for this group is sourced from transaction systems of each subordinate business segment, public market data APIs, and consolidated financial accounting modules. Full data aggregation finishes 1 to 2 hours after market close each trading day. The document structure uses hierarchical formatting. The top level includes overall group summary data. Lower levels break down detailed entries by business segments such as securities brokerage, asset management, and insurance agency. Fields include segment identifier, daily total transaction value, earnings change metric, and holding market value proportion. Total transaction value is measured in yuan. Earnings change metrics use basis points as the unit. Proportion metrics use proportional coefficients as the unit.
What constraints do these characteristics impose on multi-turn dialogue and prompt engineering
The hierarchical document structure requires multi-turn dialogue to support progressive questioning by business segment hierarchy. Prompts must clearly guide users to initiate queries by hierarchy, and retain segment hierarchy association information in context management. The fixed T+1 update rhythm requires prompts to clearly mark data update timeliness, to prevent users from mistaking the data for real-time market data. Differentiated fields across multiple business segments require prompts to predefine indicator mapping rules for each segment, to avoid confusion between definitions of earnings, total transaction value, and other metrics across different businesses. The integration of multi-source data requires the dialogue flow to verify whether the currently queried segment has loaded the corresponding data source, to avoid calls to unconfigured external data.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
maxContext | 12000–15000 characters | This group has a large volume of detailed business segment data. Multi-turn dialogue requires sufficient context to support hierarchical questioning, avoiding information loss caused by context overflow |
prompt_template | Prioritize use of holding group and each business segment data updated after the same day's market close, organize responses in a group-segment hierarchical structure, and clearly mark data update timeliness | Adapt to the hierarchical data structure and T+1 update rhythm, guide dialogue to initiate queries by business segment |
RECALL_CHUNK_COUNT | Top 8–10 entries | This group has a large number of business segments. Sufficient recalled detailed data is needed to cover common query scopes, while avoiding redundant information interfering with response accuracy |
parse_retain_old_files | Disabled | Prevent historically parsed files from being mixed into the current dialogue's data source, ensuring only market and yield data updated on the same day is loaded |
enable_variable_kb | Enabled | Support dynamically switching the corresponding knowledge base data source by business segment, adapting to the query needs of this group's multiple business segments |
dialog_auth_enable | Enabled | Ensure only authorized users can access dialogue content for yield and market daily reports, avoiding sensitive data leaks |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require individual analysis, and it is recommended to test on your own samples before finalizing settings.
Three common configuration mistakes
- Phenomenon: When parsing new market documents each time, historically parsed documents are automatically loaded into the current dialogue's data source. Cause: The
parse_retain_old_filesconfiguration item is not disabled. The system retains historically parsed files by default, which are mixed into the data scope of the current query. - Phenomenon: Unconfigured knowledge base content is automatically returned in dialogue, and irrelevant information cannot be blocked. Cause: The
prompt_templatedoes not clearly limit use of only configured market and yield data sources, or a reasonable recall threshold is not set. This causes unassociated knowledge base content to be recalled. - Phenomenon: When attempting to initiate a dialogue by passing a knowledge base ID via a variable, the system returns a parameter error prompt. Cause: The
enable_variable_kbconfiguration item is not enabled, or the variable format does not meet the system's required parameter specifications. The incoming knowledge base ID fails to be recognized.
How to confirm correct configuration
- Initiate a query for overall group yield. Verify that the response clearly marks data update timeliness, and content only covers the configured business segment scope.
- Initiate hierarchical questioning for a specified business segment. Verify that the system retains context from the previous dialogue, and correctly associates detailed data for the corresponding segment.
- Upload a test market document. Verify that the parsing process does not load historically uploaded documents, and only uses the currently uploaded data source to generate a response.
- Attempt to initiate a dialogue by passing a specified business segment knowledge base ID via a variable. Verify that the system correctly recognizes the variable and loads the corresponding data source.
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.