data-science-document-ai 1.42.5__py3-none-any.whl → 1.57.0__py3-none-any.whl

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

@@ -0,0 +1,70 @@
+{
+  "type": "OBJECT",
+  "properties": {
+      "bookingNumber": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The booking number associated with the Arrival Notice document. They are often referred to as 'Booking Number', 'Booking No.', 'Booking Ref.', 'Booking Reference', 'Booking ID', 'carrier's reference' or 'Order Ref'."
+      },
+      "destinationTerminal": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The terminal at the destination port where the container will be delivered."
+      },
+      "eta": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "Estimated Time of Arrival (ETA) is the expected date when the shipment will arrive at its destination."
+      },
+      "mblNumber": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "Bill of Lading number (B/L NO.), a document issued by the carrier."
+      },
+      "portOfDischarge": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The port where the goods are discharged from the vessel. This is the destination port for the shipment."
+      },
+      "vesselName": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The name of the vessel carrying the shipment."
+      },
+      "containers": {
+          "type": "ARRAY",
+          "items": {
+              "type": "OBJECT",
+              "properties": {
+                  "containerNumber": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The unique identifier for each container. It always starts with 4 capital letters and followed by 7 digits. Example: TEMU7972458."
+                  },
+                  "containerType": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The size of the container associated with the containerNumber, such as 20ft, 40ft, 40HC, 20DC etc."
+                  },
+                  "grossWeight": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The gross weight of the container. Usually mentioned as G.W or GW or Gross Weight, etc.."
+                  },
+                  "measurements": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The volume of the container. Usually, it is measured in 'Cubic Meter (cbm)' or dimensions. But volume in 'cbm' is preferred."
+                  },
+                  "sealNumber": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The seal number associated with the container Number. But it is not same as the container number."
+                  }
+              },
+              "required": ["containerNumber", "containerType", "grossWeight"]
+          }
+      }
+},
+  "required": ["bookingNumber", "destinationTerminal", "eta", "portOfDischarge", "vesselName", "containers"]
+}

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

@@ -0,0 +1,40 @@
+<PERSONA> You are an efficient document entity data extraction specialist working for a Freight Forwarding company. <PERSONA>
+
+<TASK> Your task is to extract data from Arrival Notice documents as per the given response schema structure. <TASK>
+
+<CONTEXT>
+The Freight Forwarding company receives Arrival Notice from shipping lines.
+These documents contain various details related to arrival of a shipment to the port of destination such as container numbers, estimated time of arrival, vessel details and containers information.
+They may be written in different languages such as English, German, Italian and can appear in a variety of formats and layouts.
+Your role is to accurately extract specific entities from these Arrival Notices to support efficient processing and accurate record-keeping.
+<CONTEXT>
+
+<INSTRUCTIONS>
+- Populate fields as defined in the response schema.
+- Multiple Containers entries may exist, capture all instances under "containers".
+- Use the data field description to understand the context of the data.
+
+- bookingNumbers:
+    - Booking numbers are unique identifiers for shipments. They are often referred to as "Booking Number", "Booking No.", "Booking Ref.", "Booking Reference", "Booking ID", "SACO-Pos.", "Order Ref", "Unsere Referenz", or "Unsere Position"
+    - If there is a unique_id that starts with "S" followed by 6 or 8 digits, it is a shipmentID, not a bookingNumber.
+
+- destinationTerminal:
+    - Destination Terminal can also be referred to as "Destination Termina;", "Pickup Location", "Delivery Location", "Delivery Terminal", "Empfangsort", "Entladeort", or "Abladestelle".
+
+- mblNumbers:
+    - Commonly known as "Bill of Lading Number", "BILL OF LADING NO.", "BL Number", "BL No.", "B/L No.", "BL-Nr.", "B/L", "HBL No.", or "M-AWB Nummer".
+    - Bill of Lading Number is known as mblNumber. Not a shipmentID even if it starts with "S".
+    - mblNumber from Hapag-Lloyd always starts with HLC.... (e.g., "HLCUTS12303AWNT3) and named as SEA WAYBILL or "SWB-NR.
+
+- eta:
+    - Estimated Time of Arrival (ETA) is the expected date and time when the shipment will arrive at the destination port.
+    - It can be referred to as "ETA", "Estimated Arrival", "Voraussichtliche Ankunft", "Ankunftszeit", "Arrivo", "Due to arrive at Terminal"
+
+- vesselName:
+    - Vessel Name is the name of the ship carrying the cargo. It can be referred to as "Vessel", "Ship Name", "Schiff", "Schiffsname", "Nave", or "Vessel/Flight No.".
+
+- containers: Details of each container on the arrival notice. Make sure to extract each container information separately.
+    - containerNumber: Container Number consists of 4 capital letters followed by 7 digits (e.g., TEMU7972458, CAIU 7222892).
+    - sealNumber: Seal numbers are unique identifiers for shipping seals. They are usually mentioned as seal numbers in the document but they are definitely not container numbers.
+
+<INSTRUCTIONS>

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

@@ -1,32 +1,146 @@
 {
   "type": "OBJECT",
   "properties": {
-    "cfsCutOff": {"type": "STRING", "nullable": true, "description": "the date by which an LCL (Less than Container Load) shipment needs to be checked in to a CFS (Container Freight Station) to meet its scheduled sailing"},
-    "bookingNumber": {"type": "STRING", "nullable": true},
-    "cyCutOff": {"type": "STRING", "nullable": true},
-    "gateInReference": {"type": "STRING", "nullable": true},
-    "gateInTerminal": {"type": "STRING", "nullable": true},
-    "mblNumber": {"type": "STRING", "nullable": true},
-    "pickUpReference": {"type": "STRING", "nullable": true},
-    "pickUpTerminal": {"type": "STRING", "nullable": true},
-    "siCutOff": {"type": "STRING", "nullable": true},
-    "vgmCutOff": {"type": "STRING", "nullable": true},
+    "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 No.', 'Booking Reference', 'Our Reference', or 'Order Ref'."
+    },
+    "contractNumber": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+    },
+    "pickUpTerminalCode": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The specific terminal for cargo pickup during the import shipment."
+    },
+    "gateInTerminalCode": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. E.g., Export terminal delivery address, Export terminal location, or Export terminal name."
+    },
+    "performaDate": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The date considered to apply the rates and charges specified in the booking confirmation"
+    },
+    "cyCutOff": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The datetime by which the cargo to be delivered to the Container Yard. It can be found with keys FCL delivery cut-off, FCL DG delivery cut-off, CY CUT OFF, CY Closing."
+    },
+    "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'."
+    },
+    "mblNumber": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "Bill of Lading number (B/L NO.), a document issued by the carrier."
+    },
+    "pickUpReference": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "A reference code for cargo pickup during the import shipment. Sometimes it can be 'Our Reference'."
+    },
+    "siCutOff": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The deadline datetime for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys Shipping Instruction Closing."
+    },
+    "vgmCutOff": {
+      "type": "STRING",
+      "nullable": true,
+        "description": "The deadline datetime for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys VGM DEADLINE, VGM DUE, VGM CUT OFF."
+    },
+    "containers": {
+      "type": "ARRAY",
+      "items": {
+        "type": "OBJECT",
+        "properties": {
+          "containerType": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The size / type of the container, such as 20ft, 40ft, 40HC, 20DC etc under Type/Size column."
+          },
+          "pickUpDepotCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The depot code where the empty container will be picked up. It is identified as Empty Pick Up Depot or Export Empty Pick Up Depot(s)."
+          },
+          "dropOffDepotCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The depot code where the empty container will be dropped off."
+          }
+        }
+      },
+      "required": ["containerType", "pickupDepotCode", "dropoffDepotCode"]
+    },
     "transportLegs": {
       "type": "ARRAY",
       "items": {
         "type": "OBJECT",
         "properties": {
-            "eta": {"type": "STRING", "nullable": true},
-            "etd": {"type": "STRING", "nullable": true},
-            "imoNumber": {"type": "STRING", "nullable": true},
-            "portOfDischarge": {"type": "STRING", "nullable": true},
-            "portOfLoading": {"type": "STRING", "nullable": true},
-            "vesselName": {"type": "STRING", "nullable": true},
-            "voyage": {"type": "STRING", "nullable": true}
-          },
-        "required": []
-      }
+          "eta": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "Estimated Time of Arrival (ETA) is the expected date when the shipment will arrive at its destination."
+          },
+          "etd": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "Estimated Time of Departure (ETD) is the expected date when the shipment will leave the origin port."
+          },
+          "imoNumber": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The International Maritime Organization number for a specific leg. It can be found as IMO No, IMO number."
+          },
+          "portOfDischarge": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The port where the goods are discharged from the vessel. This is the destination port for the shipment. It can be found at POD, Port of Discharge, To, Discharge Port"
+          },
+          "portOfLoading": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The port where the goods are loaded onto the vessel. This is the origin port for the shipment. It can be found at POL, Port of Loading, From, Load Port"
+          },
+          "vesselName": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The name of the vessel carrying the shipment. It can be found at vessel, INTENDED VESSEL/VOYAGE"
+          },
+          "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"
+          }
+        }
+      },
+      "required": [
+          "eta",
+          "etd",
+          "portOfDischarge",
+          "portOfLoading",
+          "vesselName",
+          "voyage"
+        ]
+    },
+    "carrierAddress": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The address of the carrier who provides service and issued the document."
+    },
+    "carrierName": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The name of the carrier who issued the document e,g, Hapag-Lloyd."
     }
   },
-  "required": []
+  "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]
 }

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

@@ -1,6 +1,14 @@
-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:
-```json
-{
+<PERSONA> You are an efficient document entity data extraction specialist working for a Freight Forwarding company. <PERSONA>
+
+<TASK> Your task is to extract data from Booking Confirmation documents as per the given response schema structure. <TASK>
+
+<CONTEXT>
+The Freight Forwarding company receives Booking Confirmation from EverGreen Carrier (Shipping Lines) partner.
+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.
+<CONTEXT>
+
 "mblNumber": "Extract the value after the label 'BOOKING NO.'.",
 "gateInReference": "Extract the value after the label 'BOOKING NO.'.",
 "pickUpReference": "Extract the value after the label 'BOOKING NO.'.",
@@ -14,23 +22,19 @@ your task is to extract the text value of the following entities and page number
 "portOfDischarge": "Extract the text after the label 'PORT OF DISCHARGING:' and before 'FINAL DESTINATION'.",
 "pickUpTerminal": "Extract the text after the label 'EMPTY PICK UP AT:' removing any extra spaces or line breaks.",
 "gateInTerminal": "Extract the text after the label 'FULL RETURN TO:' removing any extra spaces or line breaks.",
-"transportLegs": [
-{
-"portOfLoading": "For the first leg, use the extracted 'portOfLoading'.",
-"portOfDischarge": "Extract the text after the label 'T/S PORT OF LOADING:'.",
-"vesselName": "For the first leg, use the extracted 'vesselName'.",
-"voyage": "Voyage is a code of numbers and letters sometimes separated by '-'. For the first leg, use the extracted 'voyage'.",
-"eta": "Extract the date after the label 'ETA DATE' that appears within the section starting with 'FINAL DESTINATION:' and ending with 'T/S PORT OF LOADING:'.",
-"etd": "Extract the date after the label 'ETD DATE' that appears within the section starting with 'PORT OF LOADING:' and ending with 'FINAL DESTINATION:'.",
-},
-{
+
+"transportLegs":
+    "portOfLoading": "For the first leg, use the extracted 'portOfLoading'.",
+    "portOfDischarge": "Extract the text after the label 'T/S PORT OF LOADING:'.",
+    "vesselName": "For the first leg, use the extracted 'vesselName'.",
+    "voyage": "Voyage is a code of numbers and letters sometimes separated by '-'. For the first leg, use the extracted 'voyage'.",
+    "eta": "Extract the date after the label 'ETA DATE' that appears within the section starting with 'FINAL DESTINATION:' and ending with 'T/S PORT OF LOADING:'.",
+    "etd": "Extract the date after the label 'ETD DATE' that appears within the section starting with 'PORT OF LOADING:' and ending with 'FINAL DESTINATION:'.",
+
+
 "portOfLoading": "For the second leg, use the 'portOfDischarge' from the previous leg.",
 "portOfDischarge": "For the second leg, use the extracted 'portOfDischarge' from the main extraction.",
 "vesselName": "Extract the text after the label 'EST. CONNECT VSL/VOY:' and before the hyphen and numbers.",
 "voyage": "Voyage is a code of numbers and letters sometimes separated by '-'. Extract the code after the label 'EST. CONNECT VSL/VOY:' and after the vessel name.",
 "eta": "Extract the date after the label 'ETA DATE' that is after the line that contains 'T/S PORT OF LOADING'",
 "etd": "Extract the date after the label 'ETD DATE' that is related to the 'EST. CONNECT VSL/VOY:'. "
-}
-]
-}
-```

src/prompts/library/bookingConfirmation/hapag-lloyd/placeholders.json

@@ -1,32 +1,146 @@
 {
   "type": "OBJECT",
   "properties": {
-    "cfsCutOff": {"type": "STRING", "nullable": true, "description": "the date by which an LCL (Less than Container Load) shipment needs to be checked in to a CFS (Container Freight Station) to meet its scheduled sailing"},
-    "bookingNumber": {"type": "STRING", "nullable": true},
-    "cyCutOff": {"type": "STRING", "nullable": true},
-    "gateInReference": {"type": "STRING", "nullable": true},
-    "gateInTerminal": {"type": "STRING", "nullable": true},
-    "mblNumber": {"type": "STRING", "nullable": true},
-    "pickUpReference": {"type": "STRING", "nullable": true},
-    "pickUpTerminal": {"type": "STRING", "nullable": true},
-    "siCutOff": {"type": "STRING", "nullable": true},
-    "vgmCutOff": {"type": "STRING", "nullable": true},
+    "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 No.', 'Booking Reference', 'Our Reference', or 'Order Ref'."
+    },
+    "contractNumber": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+    },
+    "pickUpTerminalCode": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The specific terminal for cargo pickup during the import shipment."
+    },
+    "gateInTerminalCode": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. E.g., Export terminal delivery address, Export terminal location, or Export terminal name."
+    },
+    "performaDate": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The date considered to apply the rates and charges specified in the booking confirmation"
+    },
+    "cyCutOff": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The datetime by which the cargo to be delivered to the Container Yard. It can be found with keys FCL delivery cut-off, FCL DG delivery cut-off, CY CUT OFF, CY Closing."
+    },
+    "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'."
+    },
+    "mblNumber": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "Bill of Lading number (B/L NO.), a document issued by the carrier."
+    },
+    "pickUpReference": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "A reference code for cargo pickup during the import shipment. Sometimes it can be 'Our Reference'."
+    },
+    "siCutOff": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The deadline datetime for submitting the Shipping Instructions (SI) to the carrier. It can be found with keys Shipping Instruction Closing."
+    },
+    "vgmCutOff": {
+      "type": "STRING",
+      "nullable": true,
+        "description": "The deadline datetime for submitting the Verified Gross Mass (VGM) to the carrier. It can be found with keys VGM DEADLINE, VGM DUE, VGM CUT OFF."
+    },
+    "containers": {
+      "type": "ARRAY",
+      "items": {
+        "type": "OBJECT",
+        "properties": {
+          "containerType": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The size / type of the container, such as 20ft, 40ft, 40HC, 20DC etc under Type/Size column."
+          },
+          "pickUpDepotCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The depot code where the empty container will be picked up. It is identified as Empty Pick Up Depot or Export Empty Pick Up Depot(s)."
+          },
+          "dropOffDepotCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The depot code where the empty container will be dropped off."
+          }
+        }
+      },
+      "required": ["containerType", "pickupDepotCode", "dropoffDepotCode"]
+    },
     "transportLegs": {
       "type": "ARRAY",
       "items": {
         "type": "OBJECT",
         "properties": {
-            "eta": {"type": "STRING", "nullable": true},
-            "etd": {"type": "STRING", "nullable": true},
-            "imoNumber": {"type": "STRING", "nullable": true},
-            "portOfDischarge": {"type": "STRING", "nullable": true},
-            "portOfLoading": {"type": "STRING", "nullable": true},
-            "vesselName": {"type": "STRING", "nullable": true},
-            "voyage": {"type": "STRING", "nullable": true}
-          },
-        "required": []
-      }
+          "eta": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "Estimated Time of Arrival (ETA) is the expected date when the shipment will arrive at its destination."
+          },
+          "etd": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "Estimated Time of Departure (ETD) is the expected date when the shipment will leave the origin port."
+          },
+          "imoNumber": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The International Maritime Organization number for a specific leg. It can be found as IMO No, IMO number."
+          },
+          "portOfDischarge": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The port where the goods are discharged from the vessel. This is the destination port for the shipment. It can be found at POD, Port of Discharge, To, Discharge Port"
+          },
+          "portOfLoading": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The port where the goods are loaded onto the vessel. This is the origin port for the shipment. It can be found at POL, Port of Loading, From, Load Port"
+          },
+          "vesselName": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The name of the vessel carrying the shipment. It can be found at vessel, INTENDED VESSEL/VOYAGE"
+          },
+          "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"
+          }
+        }
+      },
+      "required": [
+          "eta",
+          "etd",
+          "portOfDischarge",
+          "portOfLoading",
+          "vesselName",
+          "voyage"
+        ]
+    },
+    "carrierAddress": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The address of the carrier who provides service and issued the document."
+    },
+    "carrierName": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The name of the carrier who issued the document e,g, Hapag-Lloyd."
     }
   },
-  "required": []
-}
+  "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]
+}

src/prompts/library/bookingConfirmation/hapag-lloyd/prompt.txt

@@ -1,65 +1,59 @@
-You are a document entity extraction specialist. Given a document, the explained datapoint need to extract.
+<PERSONA> You are an efficient document entity data extraction specialist working for a Freight Forwarding company. <PERSONA>
 
-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.
+<TASK> Your task is to extract data from Booking Confirmation documents as per the given response schema structure. <TASK>
 
-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
+<CONTEXT>
+The Freight Forwarding company receives Booking Confirmation from Hapag-Lloyd Carrier (Shipping Lines) partners.
+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.
 
-Keywords for datapoints:
-- bookingNumber: Our Reference
-- cyCutOff: FCL delivery cut-off
-- gateInReference: Our Reference
-- gateInTerminal: Export terminal delivery address
-- mblNumber: BL/SWB No(s).
-- pickUpReference: Export door positioning address(es)
-- siCutOff: shipping instruction closing
-- vgmCutOff: VGM cut-off
-- eta: eta, ETA
-- etd: etd, ETD
-- imoNumber: IMO No, IMO number
-- portOfDischarge: to
-- portOfLoading: from
-- vesselName: vessel
-- voyage: Voy. no
 
-Table Structure to extract transportLegs:
-- transportLegs table has following colum names: From, To, By, ETD, ETA
-- If the first leg does not have an ETD and ETA, Also By column includes following info: ["Truck", "Combined Waterway"]; skip the row, start from one row below.
+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.
+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>
 
-Further explanation for the transportLegs part as follows:
-- you must differentiate the Voyage from DP Voyage. Never used the value with the key 'DP Voyage'.
-- Vessel name is in 'By' column and under the key Vessel
-- 'eta' must be equal or later than 'etd'!
-- portOfLoading and portOfDischarge are name of the Ports. You can rely on the port names from all over the world.
-- portOfLoading and portOfDischarge distinctly denotes the name of the ports. If you find abbreviation of the port use it, if not you can use the full name of the port
-- Abbreviations most likely to be in the parentheses like follows (DEHAM).
-- Don't use the same voyage or vesselName value more than once!
-- transportLegs are separated by a horizontal line within a table.
+<INSTRUCTIONS>
+- 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 '/').
+- 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
+- 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 AG" or "Hapag-Lloyd Aktiengesellschaft" for vendorName.
 
-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.
-- If mblNumber is null, assign it the same value as bookingNumber.
+- 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.
+
+- 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).
+    - 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)".
 
-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>