What the data for this category looks like
Data for shipping port intelligent due diligence reports comes primarily from port operation daily reports, berth scheduling logs, container throughput reports, maritime supervision filing documents, and charter party attachments. Data updates occur daily or weekly. Some real-time operation data syncs hourly. Most documents use structured tables, paired with unstructured operation notes. Core fields include berth number, ship draft depth, and container throughput, with units of number, meter, and TEU respectively. Some documents include complete cross-voyage operation cycle records.
What constraints these characteristics impose on knowledge base retrieval and recall
The mixed structure of structured fields and unstructured text requires the retrieval link to support a combination of field-level precise matching and full-text retrieval. High-frequency updated data sources require the knowledge base to support incremental synchronization mechanisms. This ensures recall results include the latest daily operation data. Long-cycle cross-voyage records require retaining operation context during segmented recall. This avoids breaking complete operation workflows. Diverse unit systems require unified unit parsing before retrieval. This prevents result omissions caused by unit mismatches.
How to set the configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
Recall count | Top 8-12 entries | Shipping port due diligence reports contain multi-dimensional operation data. Too many results will exceed the context window, while too few will fail to cover the complete operation chain |
Similarity threshold | 0.75-0.85 | Structured field matching requires high precision to avoid recalling irrelevant berth or voyage data |
PARSE_FILE_TIMEOUT_SECONDS | 300 seconds | Large port log documents may contain thousands of rows of data, leading to long parsing times |
Chunk size | 1000-1200 characters | Operation process descriptions in due diligence reports require retaining complete context to avoid losing field association after splitting |
ENABLE_INCREMENTAL_SYNC | Enabled | Port data is updated at high frequency. Incremental synchronization ensures the timeliness of knowledge base data |
FIELD_PARSE_ENABLE | Enabled | Documents contain structured fields. Enabling this supports field-level precise retrieval |
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. It is recommended to test on your own samples before finalizing settings.
Three common misconfigurations
- Phenomenon: Retrieval results include voyage cost data not included in the knowledge base. Cause: The
RESTRICT_RESPONSE_TO_KNOWLEDGEconfiguration is not enabled, allowing the model to call external generation capabilities. - Phenomenon: Regular buttons cannot be used to download port log files uploaded to the knowledge base. Only the
View Original Contentlink can be used to jump to a temporary address. Cause: Public file download permissions are not configured, or the temporary address expiration mechanism is not adjusted. - Phenomenon: All bound knowledge base content is automatically recalled during retrieval, and filtering by specified voyage range is not possible. Cause: Knowledge base filtering rules are not configured via global variables, and variable assignment logic binding is not completed.
How to confirm configurations are set correctly
- Upload a recent port operation daily report, perform a retrieval, and check if the recall results include that day's data to confirm the incremental synchronization configuration is active.
- Enter structured field keywords such as "Berth 3", check if retrieval results only return documents for that berth to confirm field-level matching configuration is active.
- Test parsing documents of different lengths, check if complete operation context is retained after segmentation to confirm the
Chunk sizeconfiguration is appropriate. - Trigger a retrieval, check if returned results only come from the bound knowledge base with no external content, to confirm the range locking configuration is active.
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.