data-science-document-ai 1.45.2__tar.gz → 1.51.0__tar.gz

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: data-science-document-ai
-Version: 1.45.2
+Version: 1.51.0
 Summary: "Document AI repo for data science"
 Author: Naomi Nguyen
 Author-email: naomi.nguyen@forto.com

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "data-science-document-ai"
-version = "1.45.2"
+version = "1.51.0"
 description = "\"Document AI repo for data science\""
 authors = ["Naomi Nguyen <naomi.nguyen@forto.com>", "Kumar Rajendrababu <kumar.rajendrababu@forto.com>", "Igor Tonko <igor.tonko@forto.com>", "Osman Demirel <osman.demirel@forto.com>"]
 packages = [

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/constants.py

@@ -53,13 +53,6 @@ project_parameters = {
     "model_selector": {
         "stable": {
             "bookingConfirmation": 1,
-            "finalMbL": 0,
-            "draftMbl": 0,
-            "arrivalNotice": 0,
-            "shippingInstruction": 0,
-            "customsAssessment": 0,
-            "deliveryOrder": 0,
-            "partnerInvoice": 0,
         },
         "beta": {
             "bookingConfirmation": 0,
@@ -87,8 +80,10 @@ project_parameters = {
     # Key to combine the LLM results with the Doc Ai results
     "key_to_combine": {
         "bookingConfirmation": ["transportLegs"],
+        "arrivalNotice": ["containers"],
         "finalMbL": ["containers"],
         "draftMbl": ["containers"],
+        "deliveryOrder": ["Equipment", "TransportLeg"],
         "customsAssessment": ["containers"],
         "packingList": ["skuData"],
         "commercialInvoice": ["skus"],

data_science_document_ai-1.51.0/src/docai_processor_config.yaml

@@ -0,0 +1,22 @@
+models_project_id: "738250249861"
+model_config:
+  stable:
+    bookingConfirmation:
+      - id: "dc3e714cd168aeaa"
+        details:
+          display_name: "doc_cap_bookingConfirmation"
+          author: "reet.kanjilal@forto.com"
+          created_date: ""
+      - id: "3c280b11bdb3ed89"
+        details:
+          display_name: "doc_cap_BC_mlg"
+          author: "igor.tonko@forto.com"
+          created_date: ""
+
+  beta:
+    bookingConfirmation:
+      - id: "3c280b11bdb3ed89"
+        details:
+          display_name: "doc_cap_BC_mlg"
+          author: "igor.tonko@forto.com"
+          created_date: ""

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/excel_processing.py

@@ -11,9 +11,8 @@ import asyncio
 import numpy as np
 import pandas as pd
 
-from src.llm import prompt_excel_extraction
 from src.prompts.prompt_library import prompt_library
-from src.utils import estimate_page_count, generate_schema_structure, get_excel_sheets
+from src.utils import estimate_page_count, get_excel_sheets
 
 
 async def extract_data_from_sheet(
@@ -29,11 +28,14 @@ async def extract_data_from_sheet(
     )
 
     # Prompt for the LLM JSON
-    prompt_docai = prompt_excel_extraction(worksheet)
+    prompt = prompt_library.library[doc_type]["other"]["prompt"]
+
+    # Join the worksheet content with the prompt
+    prompt = worksheet + "\n" + prompt
 
     try:
         result = await llm_client.get_unified_json_genai(
-            prompt_docai,
+            prompt,
             response_schema=response_schema,
             doc_type=doc_type,
         )
@@ -67,19 +69,7 @@ async def extract_data_from_excel(
 
     """
     # Generate the response structure
-    response_schema = (
-        prompt_library.library[input_doc_type]["other"]["placeholders"]
-        if input_doc_type
-        in [
-            "partnerInvoice",
-            "customsInvoice",
-            "bundeskasse",
-            "commercialInvoice",
-            "packingList",
-            "bookingConfirmation",
-        ]
-        else generate_schema_structure(params, input_doc_type)
-    )
+    response_schema = prompt_library.library[input_doc_type]["other"]["placeholders"]
 
     # Load the Excel file and get ONLY the "visible" sheet names
     sheets, workbook = get_excel_sheets(file_content, mime_type)

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/llm.py

@@ -201,33 +201,4 @@ class LlmClient:
         return response
 
 
-def prompt_excel_extraction(excel_structured_text):
-    """Write a prompt to extract data from Excel files.
-
-    Args:
-        excel_structured_text (str): The structured text of the Excel file.
-
-    Returns:
-        prompt str: The prompt for common json.
-    """
-    prompt = f"""{excel_structured_text}
-
-    Task: Fill in the following dictionary from the information in the given in the above excel data.
-
-    Instructions:
-    - Do not change the keys of the following dictionary.
-    - The values should be filled in as per the schema provided below.
-    - If an entity contains a 'display_name', consider its properties as child data points in the below format.
-    {{'data-field': {{
-        'child-data-field': 'type -occurrence_type- description',
-          }}
-    }}
-    - The entity with 'display_name' can be extracted multiple times. Please pay attention to the occurrence_type.
-    - Ensure the schema reflects the hierarchical relationship.
-    - Use the data field description to understand the context of the data.
-
-    """
-    return prompt
-
-
 # pylint: enable=all

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/pdf_processing.py

@@ -202,20 +202,8 @@ async def process_file_w_llm(params, file_content, input_doc_type, llm_client):
     number_of_pages = get_pdf_page_count(file_content)
     logger.info(f"processing {input_doc_type} with {number_of_pages} pages...")
 
-    # get the schema placeholder from the Doc AI and generate the response structure
-    response_schema = (
-        prompt_library.library[input_doc_type]["other"]["placeholders"]
-        if input_doc_type
-        in [
-            "partnerInvoice",
-            "customsInvoice",
-            "bundeskasse",
-            "commercialInvoice",
-            "packingList",
-            "bookingConfirmation",
-        ]
-        else generate_schema_structure(params, input_doc_type)
-    )
+    # get the schema placeholder
+    response_schema = prompt_library.library[input_doc_type]["other"]["placeholders"]
 
     carrier = "other"
     carrier_schema = (

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/postprocessing/postprocess_partner_invoice.py

@@ -103,9 +103,18 @@ def post_process_bundeskasse(aggregated_data):
             )
 
         # Check if the deferredDutyPayer is forto
-        deferredDutyPayer = line_item.get("deferredDutyPayer", {})
-        lower = deferredDutyPayer.get("documentValue", "").lower()
-        if any(key in lower for key in ["de789147263644738", "forto"]):
+        KEYWORDS = {"de789147263644738", "forto", "009812"}
+
+        def is_forto_recipient(line_item: dict) -> bool:
+            values_to_check = [
+                line_item.get("deferredDutyPayer", {}).get("documentValue", ""),
+                line_item.get("vatId", {}).get("documentValue", ""),
+            ]
+
+            combined = " ".join(values_to_check).lower()
+            return any(keyword in combined for keyword in KEYWORDS)
+
+        if is_forto_recipient(line_item):
             is_recipient_forto = True
 
     update_recipient_and_vendor(aggregated_data, is_recipient_forto)
@@ -229,8 +238,12 @@ async def process_line_items_batch(
         [
             item.update({"reverseChargeSentence": reverse_charge})
             for item in line_items
-            if item["itemCode"]["formattedValue"] != "CDU"
+            if (
+                (item.get("itemCode") and item["itemCode"]["formattedValue"] != "CDU")
+                or not item.get("itemCode")
+            )
         ]
+
     return line_items
 
 

data_science_document_ai-1.51.0/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"]
+}

data_science_document_ai-1.51.0/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>

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/prompts/library/bundeskasse/other/placeholders.json

@@ -1,15 +1,15 @@
 {
   "type": "OBJECT",
   "properties": {
-      "currencyCode": {
+      "grandTotal": {
         "type": "STRING",
         "nullable": true,
-        "description": "The currency in which the invoice is issued."
+        "description": "The overall total amount of the invoice. It can be found with the key words Gesamtabgabenbetrag, Gesamtbetrag, or Zu erstattender Abgabenbetrag"
       },
-      "grandTotal": {
+      "currencyCode": {
         "type": "STRING",
         "nullable": true,
-        "description": "The overall total amount of the invoice."
+        "description": "The currency in which the invoice is issued. Extract the currency associated with the grand total (grandTotal) amount. It is majorly mentioned as EUR, Euro or €."
       },
       "issueDate": {
         "type": "STRING",
@@ -54,7 +54,7 @@
                   "deferredDutyPayer": {
                     "type": "STRING",
                     "nullable": true,
-                    "description": "It can be identified under \"Aufschubenhmer\" for each line item"
+                    "description": "It can be identified under 'Aufschubenhmer' for each line item"
                   },
                   "name": {
                     "type": "STRING",

{data_science_document_ai-1.45.2 → data_science_document_ai-1.51.0}/src/prompts/library/bundeskasse/other/prompt.txt

@@ -13,6 +13,7 @@ Your role is to accurately extract specific entities from these Customs invoices
 - Populate fields as defined in the response schema.
 - Multiple line item entries may exist, capture all instances under "lineItem".
 - Use the data field description to understand the context of the data.
+- The amount and the currency is always in EUR both for grandTotal and line items.
 
 - containerNumber:
     - Container Number consists of 4 capital letters followed by 7 digits (e.g., TEMU7972458, CAIU7222892).
@@ -31,15 +32,16 @@ Your role is to accurately extract specific entities from these Customs invoices
     - Credit Note Invoice Number is a unique identifier for the credit note, it starts with "ATS" only (e.g., ATS.....).
     - NIZZA is not a credit note invoice number.
 
-- grandTotal in the credit notes can be found under "Zu erstattender Abgabenbetrag".
+- grandTotal:
+    - It can be found with the key words Gesamtabgabenbetrag, Gesamtbetragin. In credit notes, it can be found under "Zu erstattender Abgabenbetrag".
+    - grandTotal value is always or mostly mentioned in EUR currency as it is issued by German Customs.
 
 - serviceDate can also be referred to as "Zollanmeldung" or "Eingangdatum" in the invoice.
 - issueDate can also be referred to as "Einfuhrabgabenbescheid" in the invoice. issueDate and serviceDate can be same in some cases.
 - vendor details can be "Hauptzollamt" details in the top portion of the invoice.
 
-- lineItem:
-    - Each line item should be extracted only once
-    - totalAmount in the Credit Note is the Differenzbetrag in the line items.
+- lineItem: Each line item should be extracted only once. Give priority to the first occurrence of the line item details in the document.
+    - totalAmount in the Credit Note is the Differenzbetrag in the line items. The totalAmount value is always or mostly mentioned in EUR currency.
     - deferredDutyPayer can be identified under "Aufschubenhmer" for each line item. It is a combination of number code and entity.
 
 You can usually find all the information in the top 2 pages of the invoice.

data_science_document_ai-1.51.0/src/prompts/library/customsAssessment/other/placeholders.json

@@ -0,0 +1,70 @@
+{
+  "type": "OBJECT",
+  "properties": {
+      "consignee": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The receiver or buyer of the goods. It can be find with the keywords like Importeur, Anmelder, Empfanger, Consignee, Buyer, Receiver, etc.."
+      },
+      "countryOfOrigin": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The country where the goods were manufactured or produced. It can be identified as Land van oorsprong, Ursprungsland in the document."
+      },
+      "MRN": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "Movement Reference Number (MRN) is a unique identifier assigned to each customs declaration for goods being imported or exported within the European Union (EU). It is used to track and monitor the movement of goods across EU member states. It can be found with MRN, Reg. Nr., Reg. Kennzeigechen, etc.."
+      },
+      "shipper": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The seller or shipper of the goods. It is often indicated by the term Shipper, Speditore, Esportatore, Exporteur, Versender."
+      },
+      "totalValueOfGoods": {
+        "type": "STRING",
+        "nullable": true,
+        "description": "The total monetary value of the goods being shipped, usually declared for customs purposes. It can be found with Waarde, Warenwert, Factuurwaarde, Invoice Value, etc.."
+      },
+      "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."
+                  },
+                  "goodsDescription": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "A brief description of the goods contained within the container. It can be found with goods description, Bezeichnung, goederenomschrijving."
+                  },
+                  "grossWeight": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The gross weight of the container. Usually mentioned as G.W or GW, Bruto, or Gross Weight, etc.."
+                  },
+                  "nettWeight": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The net weight of the goods inside the container. Usually mentioned as N.W or NW, Net Weight, or Netto, Eigenmasse, etc.."
+                  },
+                "packagingNumber": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The quantity of the goods. Usually, the quantity is in pallets, PLT, cartons, CTNS, pieces, PCS, packages, boxes, etc. Please prioritize the packaging types based on their size, as follows: Pallets (PLT) >> Cartons (CTNS) >> Pieces (PCS). Extract the Larger packaging types that will have a lower count."
+                  },
+                  "packagingType": {
+                    "type": "STRING",
+                    "nullable": true,
+                    "description": "The packaging type is the unit of packagingNumber. Example; pallets, PLT, cartons, CTNS, pieces, PCS, packages, etc. Sometimes, the packaging type is available in the column name of the packagingNumber."
+                }
+              },
+              "required": ["containerNumber", "goodsDescription", "grossWeight", "nettWeight", "packagingNumber", "packagingType"]
+          }
+      }
+},
+  "required": ["countryOfOrigin", "MRN", "totalValueOfGoods", "containers"]
+}

data_science_document_ai-1.51.0/src/prompts/library/customsAssessment/other/prompt.txt

@@ -0,0 +1,29 @@
+<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 delivery order documents as per the given response schema structure. <TASK>
+
+<CONTEXT>
+The Freight Forwarding company receives Customs Assessment from customs partners.
+These documents contain various details related to shipper, buyer, MRN, and container data such as container number, goods details at container level.
+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 Customs Assessment 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.
+
+- MRN: Movement Reference Number (MRN) is a unique identifier assigned to each customs declaration for goods being imported or exported within the European Union (EU). It is used to track and monitor the movement of goods across EU member states. It can be found with MRN, Reg. Nr., Reg. Kennzeigechen, etc..
+
+- containers: Details of each container on the Customs Assessment. 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). It can be identified as container number, cntr. nos., containernummern, cont. nr.
+    - goodsDescription: Extract only the description of the goods for the "goodsDescription" but not other information like packing, marks, etc.
+    - packagingNumber:
+        - Prioritize the "Pallets/PLTS/Cartons/CTNS/Package" over "PCS" count to extract the data for the "packagingNumber".
+        - example: If the table has "17CTNS", "9PLTS", "850", "850PCS", prioritize "9PLTS"
+        - Do not extract the pack Quantity field such as "50PCS/CTN", "5PC/Box" (these represent quantity per carton, not total shipped quantity).
+    - packagingType:
+            - Extract the unit associated with the "packagingNumber" in the table to extract the "packagingType"
+            - Sometimes it can be found on the column name of the "packagingNumber" in the table to extract the "packagingType"
+<INSTRUCTIONS>

data_science_document_ai-1.51.0/src/prompts/library/deliveryOrder/other/placeholders.json

@@ -0,0 +1,82 @@
+{
+  "type": "OBJECT",
+  "properties": {
+    "EmptyContainerDepot": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The depot where the empty container is returned."
+    },
+    "Equipment": {
+      "type": "ARRAY",
+      "items": {
+        "type": "OBJECT",
+        "properties": {
+          "CargoGrossWeight": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The gross weight of the Cargo. Usually mentioned as G.W or GW or Gross Weight, etc.."},
+          "ContainerNumber": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The container number associated with the document. They MUST consist of 4 letters followed by 7 digits (e.g., 'CMAU1234567', 'BMOU 575538/3', 'XLXU 1277652'). It can be found in the document as 'Container No.', 'Container Number', 'Cont. No.', 'Cont Nr.', 'Seefrachtcontainer-Nr.', or 'Containernummer'."},
+          "ContainerType": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The size or Type of the container associated with the containerNumber, such as 20ft, 40ft, 40HC, 20DC etc."},
+          "EmptyReturnReference": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The reference number or code for the return of the empty container."},
+          "Pin": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The PIN code associated with the container, often used for security or access purposes."},
+          "TareWeight": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The weight of the empty container itself, without any cargo inside. Usually mentioned as T.W or TW or Tare Weight, etc.."}
+        },
+        "required": ["CargoGrossWeight", "ContainerNumber", "EmptyReturnReference", "Pin", "TareWeight"]
+      }
+    },
+    "pickUpTerminal": {
+      "type": "STRING",
+      "nullable": true,
+      "description": "The terminal where the container or cargo is picked up."
+    },
+    "TransportLeg": {
+      "type": "ARRAY",
+      "items": {
+        "type": "OBJECT",
+        "properties": {
+          "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."},
+          "portOfDischarge": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The port where the goods are discharged from the vessel. This is the destination port for the shipment."},
+          "portOfLoading": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The origin port where the goods are loaded onto the vessel. Find information like 'Ladehafen' or 'Port of Loading' in the invoice."},
+          "vesselName": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The name of the vessel carrying the container or shipment"},
+          "voyage": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The unique voyage number or identifier assigned to a vessel’s specific journey. This typically corresponds to the scheduled sailing associated with the shipment and can often be found near vessel information on shipping documents. such as voyage, voy. no, voyage-no."}
+        },
+        "required": ["eta", "etd", "portOfDischarge", "portOfLoading", "vesselName", "voyage"]
+      }
+    }
+  },
+    "required": ["Equipment", "TransportLeg"]
+}

data_science_document_ai-1.51.0/src/prompts/library/deliveryOrder/other/prompt.txt

@@ -0,0 +1,36 @@
+<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 Delivery Order documents as per the given response schema structure. <TASK>
+
+<CONTEXT>
+The Freight Forwarding company receives Delivery Order from Carrier (Shipping Lines) partners.
+These documents contain various details related to shipments, equipment details, transport leg details, delivery / pickup details, vessel details, pick up terminal 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 Delivery Orders to support efficient processing and accurate record-keeping.
+<CONTEXT>
+
+<INSTRUCTIONS>
+- Populate fields as defined in the response schema.
+- Multiple Equipment and TransportLeg entries may exist — capture all instances under "Equipment" and "TransportLeg".
+- Use the data field description to understand the context of the data.
+
+EmptyContainerDepot: Empty container depot address.
+Equipment: Details of each Equipment on the Delivery Order. Make sure to extract each Equipment information separately.
+      CargoGrossWeight: Total weight of the cargo, including the tare weight of the container. Weight(incl. tare), Cargo Weight, Weight (KG)
+      ContainerNumber: Container Number consists of 4 capital letters followed by 7 digits (e.g., TEMU7972458, CAIU 7222892).
+      ContainerType: Type of the shipping container, usually related to it's size.
+      EmptyReturnReference:  A reference code for empty container return. Find it as Drop off reference, turn-in reference in the document.
+      Pin: Container release reference or PIN code to pick up the container. Can be found as Release reference, pin
+      TareWeight: Weight of the empty container without cargo. It can be found as Tare weight, tare.
+
+pickUpTerminal: The specific terminal for cargo pickup. It can also be found as  pick up at depot, empty container depot, pickup depot, empty pickup location in the doc.
+
+TransportLeg: Details of each TransportLeg on the Delivery Order. Make sure to extract each TransportLeg information separately.
+    eta: The estimated time of arrival for a specific leg.
+    etd: The estimated time of departure for a specific leg.
+    portOfDischarge: The port where cargo is unloaded.
+    portOfLoading: The port where cargo is loaded.
+    vesselName: The name of the vessel.
+    voyage: The journey or route code taken by the vessel. It is often identified as voyage, voy. no, voyage-no in the document.
+
+<INSTRUCTIONS>