About This Page
- Client industry: Aerospace equipment
- Business direction: Financial report analysis and report generation
- Capability area: Citation sources and traceability
What the Data for This Category Looks Like
Aerospace equipment enterprise financial report data primarily originates from public disclosure platforms of the Shanghai Stock Exchange and Shenzhen Stock Exchange, plus official announcement channels of corresponding military industry groups. Disclosure follows a fixed schedule: quarterly reports, semi-annual reports, and annual reports. Corresponding deadlines are within 10 days after the quarter ends, within 30 days after the quarter ends, and within four months after the fiscal year ends, respectively. Each financial report document includes structured financial statements and special notes. Fields cover general financial indicators and aerospace equipment-specific items such as military product revenue share, number of military aircraft delivered, and engine production capacity data. Units include ten thousand RMB, number of delivered units, number of produced units, and similar units.
Constraints on Citation and Traceability
The characteristics of aerospace equipment financial reports—multiple fixed disclosure sources, numerous specialized fields, and layered document structure—create three core constraints for citation traceability. First, configure data source synchronization rules that match fixed disclosure deadlines. This ensures only the latest disclosed documents for the current period are referenced, avoiding expired data. Second, limit the recall scope to the structured financial statements and corresponding special notes chapters of the financial report. This prevents irrelevant content from being recalled. Also, configure field mapping rules for specialized fields like military product revenue and delivery volume, to ensure recalled content exactly matches the original text. Third, assign a unique identifier to each disclosed document. This prevents citation confusion between same-type financial reports from different sources.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
recall_chunk_range | ["financial_statements", "notes_military"] | Core information of aerospace equipment financial reports is concentrated in structured financial statements and military product special notes. Limiting the scope filters irrelevant content and improves traceability accuracy |
datasource_sync_cron | "0 0 2 10,30,120 * * *" | Matches disclosure deadlines for quarterly reports (within 10 days after quarter end), semi-annual reports (within 30 days after quarter end), and annual reports (within 120 days after fiscal year end), ensuring synchronization with the latest current period documents |
reference_id_strategy | ["exchange_code", "disclose_date", "page_number"] | Generates a unique reference ID based on exchange announcement code, disclosure date, and page number, preventing citation marker confusion across different financial reports |
remove_reference_mark | false | Original reference markers must be retained for compliant traceability. Temporary hiding can only be configured during the output display stage |
max_recall_count | Top 6 entries | Specialized fields in aerospace equipment financial reports are widely distributed. Recalling 6 entries covers core data and avoids redundant recalled content |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Phenomenon: Generated responses contain forged citation IDs that have no corresponding financial report original text. Cause: No unique identifier rule is configured for
reference_id_strategy, and random markers generated directly by the large model are used. This results in traceability that cannot match real documents. - Phenomenon: Raw format text such as
Reference Mark: [1]remains in the output content. Cause: Theremove_reference_markparameter is not configured correctly, or the marker cleaning logic is not executed in the output process. This leads to original parsed markers being directly output. - Phenomenon: Recalled content includes non-financial report corporate dynamic announcements. Cause: The recall scope defined by
recall_chunk_rangeis not set, so daily group announcements unrelated to financial reports are recalled. This causes citation traceability to deviate from core analysis data.
How to Verify Successful Configuration
- Upload a single aerospace equipment quarterly financial report to the knowledge base, trigger the parsing process, and view the parsed document chunk list. Confirm only chunked content from structured financial statements and military product special notes is included.
- Call the large model to generate analysis content for a single financial report, check the format of citation markers, and confirm they include exchange code, disclosure date, and page number information, with no randomly generated forged IDs.
- Temporarily adjust the
datasource_sync_cronparameter to manual trigger mode, manually synchronize the data source, and confirm the latest disclosed financial report files are prioritized into the recall pool. - View the final output content, confirm original reference markers are retained as configured or have been cleaned, with no garbled residual text.
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.