What the data for this category looks like
Financial report data for the thermal category comes primarily from publicly disclosed quarterly, annual official financial reports and temporary operation announcements of public thermal power enterprises. The update rhythm aligns with financial report disclosure cycles, with fixed quarterly and annual updates, plus temporary operation adjustment announcements. Document structures include modules such as revenue details, cost composition, pipeline operation data, heating scale and service scope. Fields include thermal sales (unit: gigajoules), heating area (unit: 10,000 square meters), revenue amount (unit: yuan), pipeline operation and maintenance parameters. Some financial report notes also include specialized data such as regional heating coverage rate and unit heating energy consumption.
What constraints do these characteristics impose on knowledge base retrieval and recall?
The coexistence of fixed-cycle updates and temporary announcements requires the knowledge base to support incremental synchronization by disclosure time, and to set reasonable recall weights for temporary announcements. The presence of specialized fields and exclusive units requires matching precise keywords with units during retrieval, to avoid recalling irrelevant non-thermal category financial report content due to missing units. The multi-module document structure requires dividing chunks by financial report modules to avoid cross-module content interfering with matching accuracy. The characteristic that specialized data only appears in notes requires ensuring the knowledge base covers note content, to avoid missing key operation information.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
chunk_length | 800–1200 characters | The content of a single module of thermal financial reports is moderately sized. This range can cover core information of a single segment, avoiding cross-module splicing interfering with matching accuracy |
similarity_threshold | 0.75–0.85 | Thermal financial reports contain a large number of specialized terms and fixed fields. A threshold that is too low will easily recall irrelevant segments, while a threshold that is too high may miss relevant content. This range is calibrated for professional text matching based on actual tests |
recall_top_k | Top 6–8 results | Most thermal financial report retrieval needs target specific module data. This number of results can cover multi-dimensional associated information for a single type of query, avoiding redundant results |
rerank_top_k | Top 3–4 results | Core financial report data needs to be displayed first. The most matching content after reranking is retained for downstream analysis and generation |
PARSE_FILE_TIMEOUT_SECONDS | 120 seconds | Single thermal financial report files have relatively large volume. This duration can cover the complete parsing process, avoiding file upload failures caused by parsing timeouts |
incremental_sync_frequency | Daily | Temporary operation announcements and updated financial report data need to be synchronized. Daily incremental synchronization can ensure data timeliness |
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 specific analysis, and it is recommended to test on your own samples before finalizing settings.
Three common errors
- Phenomenon: No search results are returned after passing in the knowledge base ID, and the interface displays "No matching content". Cause: Chunking was not performed according to the modules of thermal financial reports. Long cross-module text leads to insufficient keyword matching accuracy, making it impossible to recall corresponding segments.
- Phenomenon: The file upload API returns
message: Invalid URL, code: 500. Cause: The passed thermal financial report file URL has not completed permission verification, or the URL format contains invalid characters, leading to interface parsing failure. - Phenomenon: Retrieval results only include the main content of the financial report body, and do not cover pipeline operation and maintenance data in the notes. Cause: The index switch for auxiliary data was not enabled, and only the body content was extracted during chunking, resulting in auxiliary data such as notes not being included in the knowledge base retrieval scope.
How to confirm the configuration is correct
- Upload a single thermal power quarterly financial report file, and check whether the parsed chunks in the knowledge base are split according to modules such as revenue and pipeline operation.
- Enter a search term containing a specialized unit, and verify whether the recalled results include content of the corresponding field.
- Call the retrieval API, pass the correct knowledge base ID, and check whether the number of returned results matches the preset number of recalled entries.
- View the knowledge base synchronization log to confirm whether temporary operation announcements have completed synchronization according to the set incremental cycle.
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.