data-science-document-ai 1.58.0__py3-none-any.whl → 1.60.0__py3-none-any.whl

src/prompts/library/bookingConfirmation/msc/prompt.txt

@@ -7,73 +7,70 @@ The Freight Forwarding company receives Booking Confirmation from MSC Carrier (S
 These Booking Confirmations contain various details related to booking, container pick up and drop off depot details, vessel details, as well as other transport Legs data.
 They may be written in different languages such as English, German, Vietnamese, Chinese, and other European languages, and can appear in a variety of formats and layouts.
 Your role is to accurately extract specific entities from these Booking Confirmations to support efficient processing and accurate record-keeping.
+
+To provide context on the journey of a containers for both Export and Import shipments,
+For Export shipment: An empty container is picked up from a depot (pickupDepotCode) using a pickUpReference and goods loaded into it at a warehouse. Then the loaded container / cargo is transported back to a Container Yard or gateInTerminal before the cyCutOff date for further shipping processes. Then the POL of the First TransportLeg may start from the gateInTerminal or a different POL too.
+For Import Shipment: The loaded container / cargo arrives at a port of discharge then picked up at pickUpTerminal using pickUpReference. After delivery, an empty container is returned to a depot (dropOffDepotCode).
 <CONTEXT>
 
-bookingNumber: A unique identifier for the booking.
-cyCutOff: The deadline for cargo to be delivered to the Container Yard.
-gateInReference: A reference code for cargo entering the terminal.
-gateInTerminal: The specific terminal where cargo is gated in.
-mblNumber: The Master Bill of Lading number.
-pickUpReference: A reference code for cargo pickup.
-pickUpTerminal: The specific terminal for cargo pickup.
-siCutOff: The deadline for submitting shipping instructions.
-vgmCutOff: The deadline for submitting the Verified Gross Mass of the cargo.
-transportLegs:
-    eta: The estimated time of arrival for a specific leg.
-    etd: The estimated time of departure for a specific leg.
-    imoNumber: The International Maritime Organization number for a specific leg.
-    portOfDischarge: The port where cargo is unloaded for a specific leg.
-    portOfLoading: The port where cargo is loaded for a specific leg.
-    vesselName: The name of the vessel for a specific leg.
-    voyage: The journey or route taken by the vessel for a specific leg.
+<INSTRUCTIONS>
+- gateInTerminalCode: The specific terminal where cargo is gated in. It can be called Return Equip Delivery Terminal and Location interception. This sometimes can be the same as portOfLoading of the First transportLeg.
+- gateInReference: A reference code for cargo entering the terminal. If not mentioned explicitly and gateInTerminal is extracted, then use bookingNumber as gateInReference.
+- pickUpTerminal: The specific terminal for cargo pickup. It can be found as Import pick up address(es),  PORT OF DISCHARGE (after the slash '/').
+- pickUpReference: A reference code for cargo pickup. If not mentioned explicitly and pickUpTerminal is extracted, then use bookingNumber as pickUpReference.
+
+- cyCutOff: The deadline for cargo to be delivered to the Container Yard. It can be found at CUT-OFF(Date/Time), FCL delivery cut-off, CY CUT OFF, CY Closing.
+
+- carrierName and carrierAddress:
+    - Extract the name and address of the carrier who is the main parent company in the document.
+    - It can be found in the top section of the document, often near the logo or header.
+    - Example:
+        - "MSC" for carrierName
+        - Hamburg, Germany, NETHERLANDS, Poland, Italy, Vietnam, China SHANGHAI BRANCH etc... for carrierAddress.
+
+- Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".
 
-your task is to extract the text value of the following entities and page numbers starting from 0 where the value was found in the document:
-SCHEMA_PLACEHOLDER
+- transportLegs: Multiple Transport Legs entries may exist, capture all instances under "transportLegs". Make sure the order of the legs are important.
+    - eta: The estimated time of arrival for a specific leg.
+    - etd: The estimated time of departure for a specific leg.
+    - imoNumber: The International Maritime Organization number for a specific leg.
+    - portOfDischarge: The port where cargo is unloaded for a specific leg.
+    - portOfLoading: The port where cargo is loaded for a specific leg.
+    - vesselName: The name of the vessel for a specific leg.
+    - voyage: The journey or route taken by the vessel for a specific leg.
 
-Further explanation and Keywords for the transportLegs part as follows. The below 2 conditions is crucial. Take attention here:
-- if PORT OF TRANSHIPMENT N*1 value is avaliable, it means we have the second leg, otherwise skip the second and third leg instructions, make it only one leg!
-- if PORT OF TRANSHIPMENT N*2 value is avaliable, it means we have the third leg, otherwise skip the third leg instructions, make it only two leg!
+IMPORTANT explanation for the transportLegs part as follows:
+- There is at least one leg in each document.
+- 'eta' must be equal or later than 'etd'!
+- first leg's ETD is always second value in EST. TIME OF ARRIVAL/DEPARTURE. E.g. 30/08/2025 14:00 31/10/2025 22:00 you need the select 31/10/2025 22:00.
+- Multiple legs are possible. When there are multiple legs,
+    - Sequential Sorting: You must manually re-order legs based on etd then eta, regardless of their order in the source text.
+    - "PORT OF TRANSHIPMENT N1" indicates the presence of a second leg. and "PORT OF TRANSHIPMENT N2" indicates the presence of a third leg.
+    - Transhipment Handling: Treat any mentioned "PORT OF TRANSHIPMENT N1" as the bridge between two legs (Discharge for Leg A and Loading for Leg B).
+    - The Connectivity Rule: For any sequence of legs, the Port of Discharge of the previous leg must match the Port of Loading of the following leg.
+        - PORT OF TRANSHIPMENT N1 is the Port of Discharge for the first transportLegs and Port of Loading for the second transportLegs.
+        - PORT OF TRANSHIPMENT N2 is the Port of Discharge for the second transportLegs and Port of Loading for the third transportLegs.
+    - Timeline Integrity: Ensure a "No Time Travel" policy: The eta of a previous leg must be earlier than or equal to the etd of the following leg.
 
-- first leg instructions:
-    - first leg's portOfLoading is always PLACE OF LOADING value.
-    - first leg's vesselName is always VESSEL NAME value, Ignore the paranthesis part!.
-    - first leg's portOfDischarge is PORT OF TRANSHIPMENT N*1 value if PORT OF TRANSHIPMENT N*1 value is exists.
-    - first leg's portOfDischarge is PORT OF DISCHARGE value if PORT OF TRANSHIPMENT N*1 value is not exists.
-    - first leg's voyage is always VOYAGE NUMBER value with the same row VESSEL NAME.
-    - first leg's imoNumber is in the VESSEL NAME which the number following of LLOYDS NO.
-    - first leg's eta is EST. TIME OF ARRIVAL value with the same row VESSEL NAME if PORT OF TRANSHIPMENT N*1 value is not exists.
-    - first leg's etd is always EST. TIME OF ARRIVAL/DEPARTURE second value E.g. 30/08/2023 14:00 31/08/2023 22:00 you need the select 31/08/2023 22:00.
+Structure of Multiple Leg Sequence & Mapping
+ Leg 1 (Initial):
+ - `portOfLoading`: PLACE OF LOADING.
+ - `portOfDischarge`: PORT OF TRANSHIPMENT N1 (if exists), otherwise PORT OF DISCHARGE.
+ - `vesselName`: VESSEL NAME (ignore parentheses).
+ - `imoNumber`: Number following LLOYDS NO. in Vessel Name.
+ - `etd`: 2nd timestamp in "EST. TIME OF ARRIVAL/DEPARTURE".
 
-- second leg instructions:
-    - second leg's portOfLoading is always PORT OF TRANSHIPMENT N*1 value.
-    - second leg's vesselName is always CONNECTING VESSEL N*1 value.
-    - second leg's portOfDischarge is PORT OF TRANSHIPMENT N*2 value if PORT OF TRANSHIPMENT N*2 value is exists.
-    - second leg's portOfDischarge is PORT OF DISCHARGE value if PORT OF TRANSHIPMENT N*2 value is not exists.
-    - second leg's voyage is always VOYAGE NUMBER value with the same row CONNECTING VESSEL N*1.
-    - second leg's imoNumber is in the CONNECTING VESSEL N*1 which the number following of LLOYDS NO.
-    - second leg's eta is never available so set it to null.
-    - second leg's etd is always EST. TIME OF DEPARTURE value with the same row PORT OF TRANSHIPMENT N*1.
 
-- third leg instructions:
-    - third leg's portOfLoading is always PORT OF TRANSHIPMENT N*2 value.
-    - third leg's vesselName is always CONNECTING VESSEL N*2 value.
-    - third leg's portOfDischarge is always PORT OF DISCHARGE value.
-    - third leg's voyage is always VOYAGE NUMBER value with the same row CONNECTING VESSEL N*2.
-    - third leg's imoNumber is in the CONNECTING VESSEL N*2 which the number following of LLOYDS NO.
-    - third leg's eta is never available so set it to null.
-    - third leg's etd is always EST. TIME OF DEPARTURE value with the same row PORT OF TRANSHIPMENT N*2.
+ Leg 2 (Intermediate):  Trigger: Only if PORT OF TRANSHIPMENT N1 exists.
+ - `portOfLoading`: PORT OF TRANSHIPMENT N1.
+ - `portOfDischarge`: PORT OF TRANSHIPMENT N2 (if exists), otherwise PORT OF DISCHARGE.
+ - `vesselName`: CONNECTING VESSEL N1.
+ - `etd`: EST. TIME OF DEPARTURE from Port of Transhipment row.
 
-- finalizing transporLegs:
-    - Check number of legs
-    - If the last item of the transportLegs' portOfLoading is the same value with PORT OF DISCHARGE DELETE THE ITEM!
 
-Further explanation for datapoints except transportLegs part as follows:
-- If gateInReference is null, assign it the same value as bookingNumber.
-- If pickUpReference is null, assign it the same value as bookingNumber.
+ Leg 3 (Final):  Trigger: Only if PORT OF TRANSHIPMENT N2 exists.
+ - `portOfLoading`: PORT OF TRANSHIPMENT N2.
+ - `portOfDischarge`: PORT OF DISCHARGE.
+ - `vesselName`: CONNECTING VESSEL N2.
 
-You must apply the following rules:
-- The JSON schema must be followed during the extraction.
-- The values must only include text found in the document
-- Do not normalize any entity value.
-- If an entity is not found in the document, keep it empty or np.Nan.
-- Validate the JSON make sure its a valid JSON ! No extra text, no missing comma!
+<INSTRUCTIONS>

src/prompts/library/bookingConfirmation/oocl/placeholders.json

@@ -4,12 +4,12 @@
     "bookingNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "A unique identifier assigned to the shipment booking, used for tracking and reference. They are often referred to as 'Booking Number', 'Booking No.', 'Booking Ref.', 'Booking Reference', 'Booking ID', 'carrier's reference' or 'Order Ref'."
+      "description": "A unique identifier assigned to the shipment booking, used for tracking and reference. They are often referred to as 'Booking Number', 'Booking Reference', 'carrier's reference' or 'Order Ref'."
     },
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It can be referred as Rate Agreement Number or Contract No."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -19,12 +19,12 @@
     "gateInTerminalCode": {
       "type": "STRING",
       "nullable": true,
-      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address"
+      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. E.g., FULL RETURN LOCATION"
     },
     "serviceCode": {
       "type": "STRING",
       "nullable": true,
-      "description": "The Shipping service code associated with the booking confirmation."
+    "description": "The Shipping service code associated with the booking confirmation. It can be found as SERVICE CODE"
     },
     "performaDate": {
       "type": "STRING",
@@ -39,12 +39,12 @@
     "cyCutOff": {
       "type": "STRING",
       "nullable": true,
-      "description": "The date by which the cargo to be delivered to the Container Yard. It can be found with keys FCL delivery cut-off, CY CUT OFF, CY Closing."
+      "description": "The date by which the cargo to be delivered to the Container Yard. It can be found as Intended CY CUT OFF (First Full HUB) or Intended CY CUT OFF"
     },
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Booking Number'."
     },
     "mblNumber": {
       "type": "STRING",
@@ -54,17 +54,17 @@
     "pickUpReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo pickup during the import shipment. Sometimes it can be 'Our Reference'"
+      "description": "A reference code for cargo pickup during the import shipment. Sometimes it can be 'Booking Number'."
     },
     "siCutOff": {
       "type": "STRING",
       "nullable": true,
-      "description": "The deadline date for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys SI DEADLINE, SI DUE, SI CUT OFF, B/L INSTRUCTION DEADLINE."
+      "description": "The deadline date for submitting the Shipping Instructions (SI) to the carrier. It can be found as Shipping Instruction/BL Master Due Date"
     },
     "vgmCutOff": {
       "type": "STRING",
       "nullable": true,
-        "description": "The deadline date for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys VGM DEADLINE, VGM DUE, VGM CUT OFF."
+        "description": "The deadline date for submitting the Verified Gross Mass (VGM) to the carrier. It can be found as Verified Gross Mass (VGM) Due Date"
     },
     "containers": {
       "type": "ARRAY",
@@ -79,12 +79,12 @@
           "pickUpDepotCode": {
             "type": "STRING",
             "nullable": true,
-            "description": "The depot code where the empty container will be picked up."
+            "description": "The depot code where the empty container will be picked up. It is found as EMPTY PICK UP LOCATION"
           },
           "dropOffDepotCode": {
             "type": "STRING",
             "nullable": true,
-            "description": "The depot code where the empty container will be dropped off."
+            "description": "The depot code where the empty container will be dropped off. EMPTY DROPOFF LOCATION or EMPTY RETURN LOCATION"
           }
         }
       },
@@ -153,7 +153,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document."
+      "description": "The name of the carrier who issued the document. E.g., OOCL or Orient Overseas Container Line Ltd."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

src/prompts/library/bookingConfirmation/oocl/prompt.txt

@@ -7,18 +7,43 @@ The Freight Forwarding company receives Booking Confirmation from OOCL Carrier (
 These Booking Confirmations contain various details related to booking, container pick up and drop off depot details, vessel details, as well as other transport Legs data.
 They may be written in different languages such as English, German, Vietnamese, Chinese, and other European languages, and can appear in a variety of formats and layouts.
 Your role is to accurately extract specific entities from these Booking Confirmations to support efficient processing and accurate record-keeping.
+
+To provide context on the journey of a containers for both Export and Import shipments,
+For Export shipment: An empty container is picked up from a depot (pickupDepotCode) using a pickUpReference and goods loaded into it at a warehouse. Then the loaded container / cargo is transported back to a Container Yard or gateInTerminal before the cyCutOff date for further shipping processes. Then the POL of the First TransportLeg may start from the gateInTerminal or a different POL too.
+For Import Shipment: The loaded container / cargo arrives at a port of discharge then picked up at pickUpTerminal using pickUpReference. After delivery, an empty container is returned to a depot (dropOffDepotCode).
 <CONTEXT>
 
-bookingNumber: Extract the booking number. This information can be found near the labels "BOOKING ACKNOWLEDGEMENT" or "BOOKING NUMBER".
-gateInReference: This field should have the same value as the bookingNumber.
-cyCutOff: Look for the "INTENDED FCL CY CUT-OFF" label and extract the date and time value.
-vgmCutOff: Look for the "INTENDED VGM CUT-OFF" label and extract the date and time value.
-siCutOff: Look for the "INTENDED SI CUT-OFF" label and extract the date and time value.
-pickUpTerminal: Extract the pick-up terminal information, which can be found near the "EMPTY PICKUP LOCATION" label.
-transportLegs: This field should contain a list of two dictionaries. The first dictionary represents the first transport leg, starting with the initial "PORT OF LOADING" and ending with the "TRANSSHIPMENT PORT". The second dictionary represents the second transport leg, starting with the "TRANSSHIPMENT PORT" and ending with the "FINAL DESTINATION".
-eta: Within each transport leg, extract the estimated time of arrival (ETA) value, which is usually located near the "ETA" label. Eta should be a later date than etd! Ignore the first ETA label in the document that is on the line that starts with "INTENDED VESSEL/VOYAGE". For the first transport leg the correct eta is on the line that starts with "T/S". For the second leg the correct eta is on the line that starts with "FINAL DESTINATION".
-etd: Within each transport leg, extract the estimated time of departure (ETD) value, which is usually located near the "ETD" label.
-portOfDischarge: Within the second transport leg, extract the port of discharge information, which can be found near the "PORT OF DISCHARGE" label.
-portOfLoading: Extract the port of loading information, which can be found near the "PORT OF LOADING" label.
-vesselName: Within each transport leg, extract the vessel name, which can be found near the labels "INTENDED VESSEL/VOYAGE" or "T/S INTENDED VESSEL/VOYAGE".
-voyage: Within each transport leg, extract the voyage number, which is usually located right after the vessel name.
+<INSTRUCTIONS>
+- Populate fields as defined in the response schema.
+- Use the data field description to understand the context of the data.
+
+- bookingNumber: Extract the booking number. This information can be found at the top section of the document".
+
+- gateInTerminalCode: The specific terminal where cargo is gated in. It can be called as FULL RETURN LOCATION. This sometimes can be the same as portOfLoading of the First transportLeg.
+- gateInReference: A reference code for cargo entering the terminal. If not mentioned explicitly and gateInTerminal is extracted, then use bookingNumber as gateInReference.
+- pickUpTerminal: The specific terminal for cargo pickup. It can be found as Import pick up address(es),  PORT OF DISCHARGE (after the slash '/').
+- pickUpReference: A reference code for cargo pickup. If not mentioned explicitly and pickUpTerminal is extracted, then use bookingNumber as pickUpReference.
+
+- transportLegs: Multiple Transport Legs entries may exist, capture all instances under "transportLegs". Make sure the order of the legs are important.
+    - eta: The estimated time of arrival for a specific leg.
+    - etd: The estimated time of departure for a specific leg.
+    - imoNumber: The International Maritime Organization number for a specific leg.
+    - portOfDischarge: The port where cargo is unloaded for a specific leg.
+    - portOfLoading: The port where cargo is loaded for a specific leg.
+    - vesselName: The name of the vessel for a specific leg. It can be found as INTENDED VESSEL.
+    - voyage: The journey or route taken by the vessel for a specific leg. It can be found as VOYAGE.
+
+IMPORTANT explanation for the transportLegs part as follows:
+- There is at least one leg in each document.
+- 'ETA' must be equal or later than 'ETD'!
+- first leg's ETA is always after the first leg's ETD in the document.
+- Multiple legs are possible. When there are multiple legs,
+    - Sequential Sorting: You must manually re-order legs based on etd then eta, regardless of their order in the source text.
+    - "TRANSHIPMENT PORT" indicates the presence of a second leg.
+    - Transhipment Handling: Treat any mentioned "TRANSHIPMENT PORT" as the bridge between two legs (Discharge for Leg A and Loading for Leg B).
+    - The Connectivity Rule: For any sequence of legs, the Port of Discharge of the previous leg must match the Port of Loading of the following leg.
+        - TRANSHIPMENT PORT N1 is the Port of Discharge for the first transportLegs and Port of Loading for the second transportLegs.
+        - TRANSHIPMENT PORT N2 is the Port of Discharge for the second transportLegs and Port of Loading for the third transportLegs.
+    - Timeline Integrity: Ensure a "No Time Travel" policy: The eta of a previous leg must be earlier than or equal to the etd of the following leg.
+    - Make sure the ETA and ETD values are extracted from the correct lines as per the above instructions.
+<INSTRUCTIONS>

src/prompts/library/bookingConfirmation/other/placeholders.json

@@ -19,12 +19,12 @@
     "gateInTerminalCode": {
       "type": "STRING",
       "nullable": true,
-      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address"
+      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. It can be found as Gate In At Terminal, Gate in Terminal, Full Return To Terminal, Full Return Location, Cargo Delivery At, Delivery Terminal, Full Return CY, eyc.."
     },
     "serviceCode": {
       "type": "STRING",
       "nullable": true,
-      "description": "The Shipping service code associated with the booking confirmation."
+      "description": "The Shipping service code associated with the booking confirmation. It is often referred to as 'Service Code'"
     },
     "performaDate": {
       "type": "STRING",
@@ -39,12 +39,12 @@
     "cyCutOff": {
       "type": "STRING",
       "nullable": true,
-      "description": "The date by which the cargo to be delivered to the Container Yard. It can be found with keys FCL delivery cut-off, CY CUT OFF, CY Closing."
+      "description": "The date by which the cargo to be delivered to the Container Yard. It can be found with keys CARGO CUT OFF DATE/TIME, FCL delivery cut-off, CARGO CUT-OFF (Terminal Facility), CY CUT OFF, Terminal Cut-Off, Port Cut-off Date/Time."
     },
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be load ref., Turn-in reference, or if nothing mentioned, it is booking Number."
     },
     "mblNumber": {
       "type": "STRING",
@@ -54,17 +54,17 @@
     "pickUpReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo pickup during the import shipment. Sometimes it can be 'Our Reference'"
+      "description": "A reference code for cargo pickup during the import shipment. Sometimes it can be Pick-up reference, Our Reference or Booking Number."
     },
     "siCutOff": {
       "type": "STRING",
       "nullable": true,
-      "description": "The deadline date for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys SI DEADLINE, SI DUE, SI CUT OFF, B/L INSTRUCTION DEADLINE."
+      "description": "The deadline date for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys SI DEADLINE, SI DUE, SI CUT OFF, SI General CUT OFF, B/L INSTRUCTION DEADLINE, Closing B/L Date."
     },
     "vgmCutOff": {
       "type": "STRING",
       "nullable": true,
-        "description": "The deadline date for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys VGM DEADLINE, VGM DUE, VGM CUT OFF."
+        "description": "The deadline date for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys VGM DEADLINE, VGM DUE, VGM CUT OFF, Doc Cut Off Date/Time, Closing VGM Date."
     },
     "containers": {
       "type": "ARRAY",
@@ -79,7 +79,7 @@
           "pickUpDepotCode": {
             "type": "STRING",
             "nullable": true,
-            "description": "The depot code where the empty container will be picked up."
+            "description": "The depot code where the empty container will be picked up. It can be referred as EMPTY PICK UP AT, Pick Up Depot, Empty Container Pickup Location, Empty Pick Up Location, Pick Up Preff Depot."
           },
           "dropOffDepotCode": {
             "type": "STRING",
@@ -127,12 +127,12 @@
           "vesselName": {
             "type": "STRING",
             "nullable": true,
-            "description": "The name of the vessel carrying the shipment. It can be found at vessel, INTENDED VESSEL/VOYAGE"
+            "description": "The name of the vessel carrying the shipment. It can be found at vessel, INTENDED VESSEL/VOYAGE. Need to extract the name only, excluding the voyage number. E.g., 'Maersk Alabama' from 'Maersk Alabama 123E"
           },
           "voyage": {
             "type": "STRING",
             "nullable": true,
-            "description": "The journey or route taken by the vessel for a specific leg. It can be found at Voy. no, INTENDED VESSEL/VOYAGE"
+            "description": "The journey or route taken by the vessel for a specific leg. It can be found at Voy. no, INTENDED VESSEL/VOYAGE. Need to extract the voyage number only, excluding the vessel name. E.g., '123E' from 'Maersk Alabama 123E'"
           }
         }
       },
@@ -153,7 +153,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document."
+      "description": "The name of the carrier who issued the document. E.g,, Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, Evergreen etc."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

src/prompts/library/bookingConfirmation/other/prompt.txt

@@ -18,40 +18,64 @@ For Import Shipment: The loaded container / cargo arrives at a port of discharge
 - Populate fields as defined in the response schema.
 - Use the data field description to understand the context of the data.
 
-- gateInTerminal: The specific terminal where cargo is gated in. It can be found as Export terminal delivery address, PORT OF LOADING (after the slash '/').
+- gateInTerminal: The specific terminal where cargo is gated in. It can be found as Gate In At Terminal, Gate in Terminal, Full Return To Terminal, Full Return Location, Delivery Terminal, Full Return CY, Cargo Delivery At, etc... Sometimes, it might be same as PORT OF LOADING (after the slash '/').
 - gateInReference: A reference code for cargo entering the terminal. If not mentioned explicitly and gateInTerminal is extracted, then use bookingNumber as gateInReference.
 - pickUpTerminal: The specific terminal for cargo pickup. It can be found as Import pick up address(es),  PORT OF DISCHARGE (after the slash '/').
 - pickUpReference: A reference code for cargo pickup. If not mentioned explicitly and pickUpTerminal is extracted, then use bookingNumber as pickUpReference.
 
-- cyCutOff: The deadline for cargo to be delivered to the Container Yard. It can be referred to as FCL delivery cut-off, CY CUT OFF, CY Closing - Latest Return Container Date, Cargo Cut-off deadline
-- siCutOff: The deadline for submitting shipping instructions. It can be referred to as Shipping Instruction closing, SI Cut Off, Shipping Instruction deadline, INTENDED SI CUT-OFF
+- cyCutOff: The deadline for cargo to be delivered to the Container Yard. It can be referred to as CARGO CUT OFF DATE/TIME, CARGO CUT-OFF (Terminal Facility), Terminal Cut-Off, Port Cut-off Date/Time, FCL delivery cut-off, CY CUT OFF, CY Closing - Latest Return Container Date, Cargo Cut-off deadline
+- siCutOff: The deadline for submitting shipping instructions. It can be referred to as Shipping Instruction closing, SI Cut Off, Shipping Instruction deadline, INTENDED SI CUT-OFF, SI DEADLINE, SI DUE, SI General CUT OFF, B/L INSTRUCTION DEADLINE, Closing B/L Date.
 - vgmCutOff: The deadline for submitting the Verified Gross Mass of the cargo. It can be referred to as VGM cut-off, VGM Submission Deadline, Verified Gross Mass deadline
 
 - carrierName and carrierAddress:
     - Extract the name and address of the carrier who is the main parent company in the document.
+    - Example:
+        - "Hapag-Lloyd", "MSC", "CMA CGM", "ONE", "COSCO SHIPPING", "Evergreen", "Yang Ming", "ZIM", "PIL", "HMM" etc... for carrierName
+        - Hamburg, Germany, Poland, Italy, Vietnam, China etc... for carrierAddress
+
+- Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".
+    - containerType: The type of container (e.g., 20FT, 40FT, 20ft, 40ft, 40HC, 20DC, etc...).
+    - pickupDepotCode: The code of the depot where the empty container is picked up. It can be referred as EMPTY PICK UP AT, Pick Up Depot, Empty Container Pickup Location, Empty Pick Up Location, Pick Up Preff Depot."
+    - dropOffDepotCode: The code of the depot where the empty container is dropped off. It can be referred as EMPTY RETURN TO, Empty Container Drop Off Location, Empty Return Location, Drop Off Preff Depot.
 
 - transportLegs: Multiple Transport Legs entries may exist, capture all instances under "transportLegs". Make sure the order of the legs are important.
     - eta: The estimated time of arrival for a specific leg.
-    - etd: The estimated time of departure for a specific leg.
+    - etd: The estimated time of departure for a specific leg. E,g. "EST. TIME OF ARRIVAL/DEPARTURE", Sailing Date ETS.
     - imoNumber: The International Maritime Organization number for a specific leg.
     - portOfDischarge: The port where cargo is unloaded for a specific leg.
     - portOfLoading: The port where cargo is loaded for a specific leg.
     - vesselName: The name of the vessel for a specific leg.
     - voyage: The journey or route taken by the vessel for a specific leg.
 
-- Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".
-    - containerType: The type of container (e.g., 20FT, 40FT, 20ft, 40ft, 40HC, 20DC, etc...).
-    - pickupDepotCode: The code of the depot where the empty container is picked up.
-    - dropOffDepotCode: The code of the depot where the empty container is dropped off.
-
 IMPORTANT explanation for the transportLegs part as follows:
 - There is at least one leg in each document.
 - 'eta' must be equal or later than 'etd'!
 - Multiple legs are possible. When there are multiple legs,
     - Sequential Sorting: You must manually re-order legs based on etd then eta, regardless of their order in the source text.
-    - The Connectivity Rule: For any sequence of legs, the Destination (Port of Discharge) of the previous leg must match the Origin (Port of Loading) of the following leg.
-    - Transhipment Handling: Treat any mentioned "Transhipment Port" as the bridge between two legs (Discharge for Leg A / Loading for Leg B).
+    - "PORT OF TRANSHIPMENT N1", "T/S PORT OF LOADING", "TRANSHIPMENT PORT", "Transhipment", indicates the presence of a multi-leg journey. Sometimes, Having POD of the first leg and POL of the second leg indicates a multi-leg journey as well.
+    - "PORT OF TRANSHIPMENT N1" indicates the presence of a second leg. and "PORT OF TRANSHIPMENT N2" indicates the presence of a third leg.
+    - Transhipment Handling: Treat any mentioned "PORT OF TRANSHIPMENT N1", "T/S PORT OF LOADING", "TRANSHIPMENT PORT", "Transhipment" as the bridge between two legs (Discharge for Leg A and Loading for Leg B).
+    - The Connectivity Rule: For any sequence of legs, the Port of Discharge of the previous leg must match the Port of Loading of the following leg.
+        - PORT OF TRANSHIPMENT N1 is the Port of Discharge for the first transportLegs and Port of Loading for the second transportLegs.
+        - PORT OF TRANSHIPMENT N2 is the Port of Discharge for the second transportLegs and Port of Loading for the third transportLegs.
     - Timeline Integrity: Ensure a "No Time Travel" policy: The eta of a previous leg must be earlier than or equal to the etd of the following leg.
-    - Naming Convention: Look for Port Names followed by abbreviations in parentheses, e.g., "Port Name (ABCDE)".
+    - During the multi-leg, ETA of the first leg is the ETD of the second leg at the transhipment port.
+    - If Transhipment Date is empty therefore you may keep ETA of the first leg and ETD of the second leg as null if there is a transhipment.
+
+
+Structure of Multiple Leg Sequence & Mapping
+ Leg 1 (Initial):
+ - `portOfLoading`: PLACE OF LOADING.
+ - `portOfDischarge`: PORT OF TRANSHIPMENT (if exists), otherwise PORT OF DISCHARGE or Destination.
+ - `vesselName`: VESSEL NAME (ignore parentheses).
+ - `etd`: EST. TIME OF DEPARTURE from PLACE OF LOADING.
+ - `eta`: Transhipment Date or ETA at TRANSHIPMENT (if exists), otherwise keep it null in case of multi-legs. Else, DISCHARGE Date for single leg.
+
+ Leg 2 (Intermediate):  Trigger: Only if PORT OF TRANSHIPMENT N1 exists.
+ - `portOfLoading`: PORT OF TRANSHIPMENT or POD of Leg 1
+ - `portOfDischarge`: PORT OF TRANSHIPMENT N2 (if exists), otherwise PORT OF DISCHARGE.
+ - `vesselName`: CONNECTING VESSEL.
+ - `etd`: Transhipment Date or ETD at TRANSHIPMENT (if exists), otherwise keep it null in case of multi-legs. Sometimes, it can be same as ETA of Leg 1.
+ - `eta`: ETA at PORT OF TRANSHIPMENT N2 (if exists), otherwise DISCHARGE Date.
 
 <INSTRUCTIONS>

src/prompts/library/bookingConfirmation/yangming/placeholders.json

@@ -4,12 +4,12 @@
     "bookingNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "A unique identifier assigned to the shipment booking, used for tracking and reference. They are often referred to as 'Booking Number', 'Booking No.', 'Booking Ref.', 'Booking Reference', 'Booking ID', 'carrier's reference' or 'Order Ref'."
+      "description": "A unique identifier assigned to the shipment booking, used for tracking and reference. They are often referred to as 'Booking Number', 'Booking No.', or 'Booking Reference'."
     },
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It is mentioned as SVC-NBR"
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -19,7 +19,7 @@
     "gateInTerminalCode": {
       "type": "STRING",
       "nullable": true,
-      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address"
+      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. It is mentioned as Delivery Terminal."
     },
     "serviceCode": {
       "type": "STRING",
@@ -39,12 +39,12 @@
     "cyCutOff": {
       "type": "STRING",
       "nullable": true,
-      "description": "The date by which the cargo to be delivered to the Container Yard. It can be found with keys FCL delivery cut-off, CY CUT OFF, CY Closing."
+      "description": "The date by which the cargo to be delivered to the Container Yard. It can be found with keys Cargo Cut Off."
     },
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. It can be Turn-in reference or booking Number."
     },
     "mblNumber": {
       "type": "STRING",
@@ -59,12 +59,12 @@
     "siCutOff": {
       "type": "STRING",
       "nullable": true,
-      "description": "The deadline date for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys SI DEADLINE, SI DUE, SI CUT OFF, B/L INSTRUCTION DEADLINE."
+      "description": "The deadline date for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys Closing Date B/L."
     },
     "vgmCutOff": {
       "type": "STRING",
       "nullable": true,
-        "description": "The deadline date for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys VGM DEADLINE, VGM DUE, VGM CUT OFF."
+        "description": "The deadline date for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys Closing Date VGM."
     },
     "containers": {
       "type": "ARRAY",
@@ -79,7 +79,7 @@
           "pickUpDepotCode": {
             "type": "STRING",
             "nullable": true,
-            "description": "The depot code where the empty container will be picked up."
+            "description": "The depot code where the empty container will be picked up. Key to find is 'Pick Up Depot'."
           },
           "dropOffDepotCode": {
             "type": "STRING",
@@ -117,22 +117,22 @@
           "portOfDischarge": {
             "type": "STRING",
             "nullable": true,
-            "description": "The port where the goods are discharged from the vessel. This is the destination port for the shipment."
+            "description": "The port where the goods are discharged from the vessel. This is the destination port for the shipment. It is referred as Discharge"
           },
           "portOfLoading": {
             "type": "STRING",
             "nullable": true,
-            "description": "The port where the goods are loaded onto the vessel. This is the origin port for the shipment."
+            "description": "The port where the goods are loaded onto the vessel. This is the origin port for the shipment. It is referred as Sailing"
           },
           "vesselName": {
             "type": "STRING",
             "nullable": true,
-            "description": "The name of the vessel carrying the shipment. It can be found at vessel, INTENDED VESSEL/VOYAGE"
+            "description": "The name of the vessel carrying the shipment. It can be found at VESSEL/VOYAGE e,.g. 'MAERSK LINE"
           },
           "voyage": {
             "type": "STRING",
             "nullable": true,
-            "description": "The journey or route taken by the vessel for a specific leg. It can be found at Voy. no, INTENDED VESSEL/VOYAGE"
+            "description": "The journey or route taken by the vessel for a specific leg. It can be found at VESSEL/VOYAGE e.g. '123W'"
           }
         }
       },