Data for This Category
Data sources for shipping port financial and insurance-related business include:
- Structured business reports from port operation management systems
- Officially published route and berth information
- Text and PDF promotional content from the marketing material library of financial services such as cargo insurance
- Conversation logs from customer inquiries
Structured reports update daily or hourly, and include fields such as berth number, vessel name, berthing time, and throughput. Primary units are tons and TEU (twenty-foot equivalent unit). Unstructured marketing materials update irregularly, and mostly consist of documents introducing routes or insurance products. Conversation logs are natural language texts covering customer inquiries about schedules, premiums, shipping space and other business topics.
Constraints Imposed on Multi-turn Dialogue and Prompt Engineering
Structured business data for financial and insurance services has clear industry standards for fields and units. Prompts must predefine field matching rules and units to prevent confusion during model extraction. Real-time updated schedule and berth data requires multi-turn dialogue to automatically filter expired context. The valid duration and number of conversation turns must be limited. Unstructured marketing materials are mostly long documents. Multi-turn dialogue must support segmented recall and targeted extraction, and prompts must clearly specify extraction scenarios (such as cargo insurance preferential information for freight forwarder clients). A large number of professional terms exist in shipping port business. Prompts must include built-in term mapping rules to ensure the accuracy of dialogue content.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
maxContext | Previous 10 conversation turns + context from the last 2 hours | Port financial marketing conversations mostly involve real-time schedules and premiums. Overly long context introduces expired data. Limiting turn count and duration ensures conversation accuracy |
UPLOAD_FILE_MAX_SIZE | 200 MB | Common port documents such as container detail reports and insurance product brochures are large files. This value covers most business scenarios |
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Parsing large structured reports requires extended processing time to avoid parsing failure due to timeout |
modelSelectScope | All models in the GLM series and GPT series | Adapts to different computing power costs and business needs, and supports models accessed via external interfaces |
ragRecallTopK | Top 6 recall results | Balances conversation response speed and content relevance, prevents excessive recall content from causing model confusion |
promptTemplate | Add the fixed prefix "All data must match the current conversation's schedule or route, and units must be unified as TEU or tons" | Clarifies business rules to avoid mismatches between field units and business standards |
The parameter values provided on this page are common recommendations for establishing configuration baselines. Actual values are affected by material format, data volume and business rules. Specific issues require individual analysis, and it is recommended to test on your own samples before finalizing settings.
Three Common Configuration Mistakes
- Phenomenon: Only GPT series models appear in the model selection interface, and GLM series models cannot be selected. Cause: GLM series models have not been configured for access in the platform's model management module, only external interface docking has been completed.
- Phenomenon: File upload fails when calling the dialogue interface, returning a
400 Bad Requesterror. Cause: ThefileListarray field is not correctly passed in the request body, or the file upload whitelist path is not configured. - Phenomenon: Unit confusion occurs in multi-turn dialogue, such as incorrectly labeling container quantities as tons. Cause: The prompt does not clearly specify unit rules for structured data, leading the model to fail to match standard port business units during field extraction.
How to Verify Successful Configuration
- Initiate a test conversation containing port business terms, and verify that the field units returned by the model conform to business standards.
- Upload common Excel reports or PDF promotional documents for ports, and confirm that parsed data fields are complete and formatted correctly.
- Add GLM series models in the external interface, refresh the model selection interface, and confirm that target models are displayed in the list.
- After configuring multi-turn dialogue context, initiate a conversation with more than 3 consecutive schedule inquiries, and confirm that the model correctly associates vessel information from historical conversations.
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.