What the data for this category looks like
Data sources are official disclosure platforms of domestic stock exchanges and public reports from industry associations. Updates follow the schedule of periodic report releases: quarterly reports are published within 10 days after the quarter end, and annual reports are published within 4 months after the year end. Document structures include consolidated financial statements, detailed segment revenue breakdowns, production capacity and shipment volume statistics. Fields include revenue, net profit, shipment volume, yield rate, production capacity, etc. Most units are ten thousand yuan, ten thousand units, square meters. Most financial report files are in PDF format, with a single annual report typically over 100 pages long, containing multiple detailed tables and business explanations.
What constraints these characteristics impose on multi-turn dialogue and prompting
Data update timelines are concentrated and fixed. Multi-turn dialogue must clearly match the reporting period of the current query to avoid calling outdated financial report data. There are many segment business fields, so prompts must specify the query scope for the corresponding business segment to avoid confusing revenue data across different product lines such as panels, chips, and modules. The presence of non-financial fields such as shipment volume and yield rate requires support for cross-field associated queries in dialogue, such as calculating unit selling price by combining revenue and shipment volume. Documents are lengthy, so single-round parsed text fragments must fit the scale of financial reports, and the context window must retain financial report fragments from multiple rounds of inquiries to avoid losing key information during associated queries.
Configuration Settings
| Configuration Item | Recommended Values | Rationale |
|---|---|---|
maxContext | 4000–8000 characters | Fits the parsed fragment length of single optical and optoelectronic financial report files, retains context association for multi-turn dialogue |
UPLOAD_FILE_MAX_SIZE | 50–100 MB | Annual financial report PDFs often contain multiple detailed pages, requires support for larger file uploads |
PARSE_FILE_TIMEOUT_SECONDS | 300–600 seconds | Long financial report parsing requires extended processing time to avoid mid-process timeouts |
chunkSize | 1000–1500 characters | Matches logical units of financial fields when splitting financial report text, avoids truncation across fields |
recallTopK | Top 3–5 entries | Optical and optoelectronic financial reports have many segment fields, controlling the number of recalled entries avoids interference from redundant information |
promptLanguage | zh-CN / switch to en-US as needed | Adapts terminology conventions for domestic or overseas financial report disclosures, supports multi-language query needs |
The parameter values provided on this page are general recommendations used as a starting point for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require case-by-case analysis, and it is recommended to test on your own samples before finalizing settings.
Three Common Mistakes
- Phenomenon: After uploading a financial report file via the dialogue interface, "file parsing failed" or "file size exceeds limit" is returned. Cause:
UPLOAD_FILE_MAX_SIZEis not configured to a value adapted to the financial report file size, or PDF format parsing support is not enabled. - Phenomenon: Unable to associate the previously specified reporting period after consecutive multi-turn dialogue, returning irrelevant financial report data. Cause: The
maxContextparameter is not configured, or its value is too small, causing the context to be truncated and unable to retain previous query conditions. - Phenomenon: When querying financial report data with English prompts, the returned terminology does not match domestic disclosure habits, such as incorrect translation of "panel shipment volume". Cause: The
promptLanguageparameter is not switched toen-US, or industry-specific terminology mapping rules are not configured.
How to Verify Proper Configuration
- Upload a single optical and optoelectronic annual report PDF, verify that the parsed results include exclusive fields such as segment business and production capacity.
- Initiate two associated inquiries: first specify a specific reporting period, then query segment data based on that period, confirm that the returned results are associated with the same reporting period.
- Switch the
promptLanguageparameter toen-US, initiate an English query, verify that the returned terminology matches industry standard expressions. - Upload both the financial report PDF and industry analysis images at the same time, check whether the parsed results integrate information from both types of files.
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.