What the Data for This Category Looks Like
Coke-related research reports and market data are primarily sourced from monthly supply and demand reports, public market data, securities firm industry research reports, and daily spot market quotes from major domestic producing areas. Spot quotes are updated daily. Industry supply and demand reports are published monthly. Securities firm research reports are released irregularly alongside industry developments.
A single research report typically includes four sections: supply and demand fundamentals analysis, price fluctuation attribution, linked data from the downstream steel industry, and future market outlook. Core fields include average producing area quotes, steel mill procurement costs, and port inventory levels, with units of yuan/ton, yuan/ton, and ten thousand tons respectively.
What Constraints These Characteristics Impose on Knowledge Base Retrieval and Recall
The update cycles of multi-source data vary significantly. Priority rules must be configured in the recall logic to prioritize spot quotes from the last 24 hours and latest research reports from the last 7 days.
Core fields contain numerical data with multiple units. Unit formats must be unified during the preprocessing stage to avoid missed recalls caused by unit mismatches.
The text length of individual research reports varies widely. When splitting long research reports into paragraphs, core field associations must be retained to prevent key supply and demand information from being truncated.
Cross-document linked indexes must be established for data linked to the downstream steel industry, to ensure that relevant linked analysis content is recalled simultaneously during retrieval.
How to Set the Configurations
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
Recall Count | Top 10 | Core supply and demand and price information for coke research reports is usually concentrated in the top few retrieval results. Excessive recall increases the context processing burden |
Similarity Threshold | 0.72–0.85 | There are many professional terms in the coke field. This range filters low-match irrelevant documents while retaining relevant content within the specialized domain |
Chunk Length | 800–1200 characters | Core fields and analysis content of a single coke research report are usually distributed within this length range, avoiding truncation of key information |
PARSE_FILE_TIMEOUT_SECONDS | 120 seconds | OCR and text parsing for long-text research reports requires longer processing time to prevent parsing timeout failures |
UPLOAD_FILE_MAX_SIZE | 50 MB | PDF or TXT files for individual coke research reports usually do not exceed this size, while also avoiding excessive storage resource usage |
Reranked Return Count | Top 5 | Professional content in the coke field has strong relevance. The top 5 reranked results can cover the core retrieval needs of users |
The parameter values provided on this page are common starting points for configuration setup. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. It is recommended to test using local samples before finalizing settings.
Three Common Mistakes
- Phenomenon: When calling the knowledge base retrieval interface, a single query takes more than 30 seconds, and returned results have significant delays. Cause: No reasonable chunk length and recall count are configured for long-text coke research reports, causing the system to load excessive redundant documents for matching.
- Phenomenon: When selecting reference variables in the retrieval configuration interface, no optional options appear in the drop-down menu. Cause: No structured field extraction rules are configured in advance for coke research reports uploaded to the knowledge base, so the system cannot recognize available reference variables.
- Phenomenon: When inserting coke research reports into the knowledge base via API, an error prompt about parameters is returned. Cause: The
UPLOAD_FILE_MAX_SIZEparameter is not set according to configuration requirements, and the uploaded research report file exceeds the limit size.
How to Confirm the Configuration Is Correctly Set
- Upload a test coke research report, view the parsed structured field list, and confirm that core fields such as average producing area quotes and port inventory levels have been correctly extracted.
- Initiate a retrieval query for coke spot prices, view the time taken for returned results, and confirm that the time meets business expectations.
- Adjust the
similarity thresholdandrecall countparameters, initiate multiple retrievals, compare the relevance and quantity of returned results, and confirm that the configuration meets retrieval needs. - Call the knowledge base insertion API to upload a test file, confirm that the interface returns a successful status code with no parameter error prompts.
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.