data-science-document-ai 1.13.0__py3-none-any.whl → 1.56.1__py3-none-any.whl

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

@@ -1,50 +1,36 @@
-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>
 
+<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:
-      CargoGrossWeight: Total weight of the cargo, including the tare weight of the container.
-      ContainerNumber: Unique ID for tracking the shipping container.
+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.
-      Pin: Container release reference.
-      TareWeight: Tare weight.
-pickUpTerminal: The specific terminal for cargo pickup.
-TransportLeg:
+      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.
-
-Your task is to extract the text value of the following entities:
-SCHEMA_PLACEHOLDER
-
-Keywords for datapoints:
-- EmptyContainerDepot: Empty Container Depot
-- Equipment:
-      - CargoGrossWeight: Weight(incl. tare), Cargo Weight, Weight (KG)
-      - ContainerNumber: Container, Container Number, Container No.
-      - ContainerType: Type, Size/type
-      - EmptyReturnReference:  Drop off reference, turn-in reference
-      - Pin: Release reference, pin
-      - TareWeight: Tare weight, tare
-- pickUpTerminal: pick up at depot, empty container depot, pickup depot, empty pickup location
-- TransportLeg:
-    - eta: eta, ETA
-    - etd: etd, ETD
-    - portOfDischarge: to, PORT OF DISCHARGE
-    - portOfLoading: from, PORT OF LOADING
-    - vesselName: vessel
-    - voyage: voyage, voy. no, voyage-no.
-
+    voyage: The journey or route code taken by the vessel. It is often identified as voyage, voy. no, voyage-no in the document.
 
-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.
-- 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
-- Validate the JSON make sure it is a valid JSON ! No extra text, no missing comma!
-- Add an escape character (backwards slash) in from of all quotes in values
+<INSTRUCTIONS>

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

@@ -4,77 +4,77 @@
     "blNumber": {
       "type": "string",
       "nullable": true,
-      "description": ""
-    },
-    "voyage": {
-      "type": "string",
-      "nullable": true,
-      "description": ""
-    },
-    "portOfLoading": {
-      "type": "string",
-      "nullable": true,
-      "description": ""
-    },
-    "portOfDischarge": {
-      "type": "string",
-      "nullable": true,
-      "description": ""
+      "description": "The Bill of Lading number associated with the document. 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' in the document."
     },
     "bookingNumber": {
       "type": "string",
       "nullable": true,
-      "description": ""
+      "description": " 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.' or 'Order Ref'"
     },
     "containers": {
       "type": "ARRAY",
       "items": {
         "type": "OBJECT",
         "properties": {
+          "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": ""
+            "description": "The size or Type of the container associated with the containerNumber, such as 20ft, 40ft, 40HC, 20DC etc."
           },
           "grossWeight": {
             "type": "string",
             "nullable": true,
-            "description": ""
+            "description": "The gross weight of the container. Usually mentioned as G.W or GW or Gross Weight, etc.."
           },
           "measurements": {
             "type": "string",
             "nullable": true,
-            "description": ""
-          },
+            "description": "The volume of the Container. Usually, it is measured in 'Cubic Meter (cbm)' or dimensions. But volume in 'cbm' is preferred."
+            },
           "packageQuantity": {
             "type": "string",
             "nullable": true,
-            "description": ""
+            "description": "The quantity of the goods in the container. Usually 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."
           },
           "packageType": {
             "type": "string",
             "nullable": true,
-            "description": ""
-          },
-          "containerNumber": {
-            "type": "string",
-            "nullable": true,
-            "description": ""
-          },
+            "description": "The packaging type is the unit of packageQuantity. Example; pallets, PLT, cartons, CTNS, pieces, PCS, packages, etc. Sometimes, the packaging type is available in the column name of the quantityShipped."
+        },
           "sealNumber": {
             "type": "string",
             "nullable": true,
-            "description": ""
+            "description": "The seal number associated with the container Number and you can find like seal number, seal nos., shipper seal, seal.. But it is not same as the container number."
           }
         },
-        "required": []
+        "required": ["containerNumber", "containerType", "grossWeight", "measurements", "packageQuantity", "packageType", "sealNumber"]
       }
     },
+    "portOfDischarge": {
+      "type": "string",
+      "nullable": true,
+      "description": "The port where the containers are discharged from the vessel. This is the destination port for the shipment. Find information like port of discharge, pod, delivery, to."
+    },
+    "portOfLoading": {
+      "type": "string",
+      "nullable": true,
+      "description": "The origin port where the containers are loaded onto the vessel. Find information like 'Ladehafen', 'Port of Loading', 'pol', or 'from.' in the document."
+    },
+    "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."
+    },
     "vessel": {
       "type": "string",
       "nullable": true,
-      "description": ""
+      "description": "The name of the vessel carrying the container or shipment"
     }
   },
-  "required": []
+  "required": ["blNumber", "bookingNumber", "containers", "portOfDischarge", "portOfLoading", "voyage", "vessel"]
 }

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

@@ -1,44 +1,34 @@
-You are a document entity extraction specialist. Given a document, the explained datapoint need to extract.
-
-blNumber: Bill of Lading number.
-voyage: The journey or route code taken by the vessel.
-portOfLoading: The port where cargo is loaded.
-portOfDischarge:  The port where cargo is unloaded.
-bookingNumber: A unique identifier for the booking.
-containers:
-    containerType: Type of the shipping container, usually related to it's size.
-    grossWeight: Total weight of the cargo, including the tare weight of the container.
-    measurements: Dimensions of the cargo (length, width, height) for freight calculations.
-    packageQuantity: package quantity.
-    packageType: Type of packaging used (e.g., cartons, pallets, barrels).
-    containerNumber: Unique ID for tracking the shipping container.
-    sealNumber: Number of the container's seal.
-vessel: The name of the vessel.
-
-
-Your task is to extract the text value of the following entities:
-
-Keywords for datapoints:
-- blNumber: Bill of Lading number, bill of landing no., swb-no., b/l no.
-- voyage: voyage, voy. no, voyage-no.
-- portOfLoading: port of loading, pol, from.]
-- portOfDischarge: port of discharge, pod, delivery, to
-- bookingNumber: Our reference, booking no., carrier reference
-- containers:
-    - containerType: x 40' container
-    - grossWeight: gross weight
-    - measurements: Dimensions of the cargo (length, width, height) for freight calculations
-    - packageQuantity: package quantity, number and kind of packages
-    - packageType: Type of packaging used (e.g., cartons, pallets, barrels), number and kind of packages, description of goods
-    - containerNumber: container number, cntr. nos.
-    - sealNumber: seal number, seal nos., shipper seal, seal.
-- vessel: vessel
-
-
-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 'sealNumber' is not found don't add it to the result.
-- Validate the JSON make sure it is a valid JSON ! No extra text, no missing comma!
-- Add an escape character (backwards slash) in from of all quotes in values
+<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 draftMBL documents as per the given response schema structure. <TASK>
+
+<CONTEXT>
+The Freight Forwarding company receives draftMBL from Carrier (Shipping Lines) partners.
+These documents contain various details related to shipments, booking details, vessel details, POL, POD and containers 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 draftMBLs 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.
+
+- bookingNumber:
+    - 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.
+
+- blNumber:
+    - 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".
+    - blNumber from Hapag-Lloyd always starts with HLC.... (e.g., "HLCUTS12303AWNT3) and named as SEA WAYBILL or "SWB-NR.
+
+- 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 draftMBL. 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/finalMbL/other/placeholders.json

@@ -4,77 +4,77 @@
     "blNumber": {
       "type": "string",
       "nullable": true,
-      "description": ""
-    },
-    "voyage": {
-      "type": "string",
-      "nullable": true,
-      "description": ""
-    },
-    "portOfLoading": {
-      "type": "string",
-      "nullable": true,
-      "description": ""
-    },
-    "portOfDischarge": {
-      "type": "string",
-      "nullable": true,
-      "description": ""
+      "description": "The Bill of Lading number associated with the document. 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' in the document."
     },
     "bookingNumber": {
       "type": "string",
       "nullable": true,
-      "description": ""
+      "description": " 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.' or 'Order Ref'"
     },
     "containers": {
       "type": "ARRAY",
       "items": {
         "type": "OBJECT",
         "properties": {
+          "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": ""
+            "description": "The size or Type of the container associated with the containerNumber, such as 20ft, 40ft, 40HC, 20DC etc."
           },
           "grossWeight": {
             "type": "string",
             "nullable": true,
-            "description": ""
+            "description": "The gross weight of the container. Usually mentioned as G.W or GW or Gross Weight, etc.."
           },
           "measurements": {
             "type": "string",
             "nullable": true,
-            "description": ""
-          },
+            "description": "The volume of the Container. Usually, it is measured in 'Cubic Meter (cbm)' or dimensions. But volume in 'cbm' is preferred."
+            },
           "packageQuantity": {
             "type": "string",
             "nullable": true,
-            "description": ""
+            "description": "The quantity of the goods in the container. Usually 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."
           },
           "packageType": {
             "type": "string",
             "nullable": true,
-            "description": ""
-          },
-          "containerNumber": {
-            "type": "string",
-            "nullable": true,
-            "description": ""
-          },
+            "description": "The packaging type is the unit of packageQuantity. Example; pallets, PLT, cartons, CTNS, pieces, PCS, packages, etc. Sometimes, the packaging type is available in the column name of the quantityShipped."
+        },
           "sealNumber": {
             "type": "string",
             "nullable": true,
-            "description": ""
+            "description": "The seal number associated with the container Number and you can find like seal number, seal nos., shipper seal, seal.. But it is not same as the container number."
           }
         },
-        "required": []
+        "required": ["containerNumber", "containerType", "grossWeight", "measurements", "packageQuantity", "packageType", "sealNumber"]
       }
     },
+    "portOfDischarge": {
+      "type": "string",
+      "nullable": true,
+      "description": "The port where the containers are discharged from the vessel. This is the destination port for the shipment. Find information like port of discharge, pod, delivery, to."
+    },
+    "portOfLoading": {
+      "type": "string",
+      "nullable": true,
+      "description": "The origin port where the containers are loaded onto the vessel. Find information like 'Ladehafen', 'Port of Loading', 'pol', or 'from.' in the document."
+    },
+    "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."
+    },
     "vessel": {
       "type": "string",
       "nullable": true,
-      "description": ""
+      "description": "The name of the vessel carrying the container or shipment"
     }
   },
-  "required": []
-}
+  "required": ["blNumber", "bookingNumber", "containers", "portOfDischarge", "portOfLoading", "voyage", "vessel"]
+}

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

@@ -1,44 +1,34 @@
-You are a document entity extraction specialist. Given a document, the explained datapoint need to extract.
-
-blNumber: Bill of Lading number.
-voyage: The journey or route code taken by the vessel.
-portOfLoading: The port where cargo is loaded.
-portOfDischarge:  The port where cargo is unloaded.
-bookingNumber: A unique identifier for the booking.
-containers:
-    containerType: Type of the shipping container, usually related to it's size.
-    grossWeight: Total weight of the cargo, including the tare weight of the container.
-    measurements: Dimensions of the cargo (length, width, height) for freight calculations.
-    packageQuantity: package quantity.
-    packageType: Type of packaging used (e.g., cartons, pallets, barrels).
-    containerNumber: Unique ID for tracking the shipping container.
-    sealNumber: Number of the container's seal.
-vessel: The name of the vessel.
-
-
-Your task is to extract the text value of the following entities:
-
-Keywords for datapoints:
-- blNumber: Bill of Lading number, bill of landing no., swb-no., b/l no.
-- voyage: voyage, voy. no, voyage-no.
-- portOfLoading: port of loading, pol, from.]
-- portOfDischarge: port of discharge, pod, delivery, to
-- bookingNumber: Our reference, booking no., carrier reference
-- containers:
-    - containerType: x 40' container
-    - grossWeight: gross weight
-    - measurements: Dimensions of the cargo (length, width, height) for freight calculations
-    - packageQuantity: package quantity, number and kind of packages
-    - packageType: Type of packaging used (e.g., cartons, pallets, barrels), number and kind of packages, description of goods
-    - containerNumber: container number, cntr. nos.
-    - sealNumber: seal number, seal nos., shipper seal, seal.
-- vessel: vessel
-
-
-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 'sealNumber' is not found don't add it to the result.
-- Validate the JSON make sure it is a valid JSON ! No extra text, no missing comma!
-- Add an escape character (backwards slash) in from of all quotes in values
+<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 finalMBL documents as per the given response schema structure. <TASK>
+
+<CONTEXT>
+The Freight Forwarding company receives finalMBL from Carrier (Shipping Lines) partners.
+These documents contain various details related to shipments, booking details, vessel details, POL, POD and containers 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 finalMBLs 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.
+
+- bookingNumber:
+    - 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.
+
+- blNumber:
+    - 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".
+    - blNumber from Hapag-Lloyd always starts with HLC.... (e.g., "HLCUTS12303AWNT3) and named as SEA WAYBILL or "SWB-NR.
+
+- 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 finalMBL. 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/packingList/other/placeholders.json

@@ -0,0 +1,98 @@
+{
+  "type": "OBJECT",
+  "properties": {
+    "buyer": {
+      "type": "string",
+      "nullable": true,
+      "description": "The receiver or buyer of the goods."},
+    "grossWeight": {
+      "type": "string",
+      "nullable": true,
+      "description": "The total gross weight of all the goods. Usually mentioned as G.W or GW or Gross Weight, etc.."},
+    "invoiceNumber": {
+      "type": "string",
+      "nullable": true,
+      "description": "The invoice number"},
+    "netWeight": {
+      "type": "string",
+      "nullable": true,
+      "description": "The total net weight of all the goods. Usually mentioned as N.W or NW or Net Weight, etc.."},
+    "seller": {
+      "type": "string",
+      "nullable": true,
+      "description": "The seller or shipper of the goods."},
+    "skuData": {
+      "type": "ARRAY",
+      "items": {
+        "type": "OBJECT",
+        "properties": {
+          "containerNumber": {
+            "type": "string",
+            "nullable": true,
+            "description": "Container Number consists of 4 capital letters followed by 7 digits. Example: TEMU7972458. Usually mentioned as Container Number, CONTAINER NO. or Containers"},
+          "grossWeight": {
+            "type": "string",
+            "nullable": true,
+            "description": "The gross weight of the goods. Usually mentioned as G.W or GW or Gross Weight, etc.."},
+          "hsCode": {
+            "type": "string",
+            "nullable": true,
+            "description": "The harmonized system code of a goods."},
+          "measurements": {
+            "type": "string",
+            "nullable": true,
+            "description": "The volume of the goods. Usually, it is measured in 'Cubic Meter (cbm)' or dimensions. But volume in 'cbm' is preferred."},
+          "netWeight": {
+            "type": "string",
+            "nullable": true,
+            "description": "The net weight of the goods. Usually mentioned as N.W or NW or Net Weight, etc.."},
+          "packagingType": {
+            "type": "string",
+            "nullable": true,
+            "description": "The packaging type is the unit of quantityShipped. Example; pallets, PLT, cartons, CTNS, pieces, PCS, packages, etc. Sometimes, the packaging type is available in the column name of the quantityShipped."},
+          "poNumber": {
+            "type": "string",
+            "nullable": true,
+            "description": "Purchase order of the goods."},
+          "poPosition": {
+            "type": "string",
+            "nullable": true,
+            "description": "PO position refers to the specific item or line associated with a Purchase Order (PO). It represents the position or line number in the PO that corresponds to the items being shipped."},
+          "quantityShipped": {
+            "type": "string",
+            "nullable": true,
+            "description": "The quantity of the goods. Usually 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."},
+          "sealNumber": {
+            "type": "string",
+            "nullable": true,
+            "description": "A unique number associated with the container number"},
+          "skuDescription": {
+            "type": "string",
+            "nullable": true,
+            "description": "Description of the goods."},
+          "skuNumbers": {
+            "type": "string",
+            "nullable": true,
+            "description": "SKU number of the goods."}
+        },
+        "required": [
+          "skuNumbers",
+          "quantityShipped",
+          "skuDescription",
+          "grossWeight",
+          "netWeight",
+          "packagingType"
+        ]
+      }
+    },
+    "totalPackagingType": {
+      "type": "string",
+      "nullable": true,
+      "description": "The packaging type of all the goods associated with the totalQuantityShipped. It is the unit of totalQuantityShipped. Usually pallets, PLT, cartons, CTNS, pieces, PCS, packages, etc."},
+    "totalQuantityShipped": {
+      "type": "string",
+      "nullable": true,
+      "description": "The total quantity of the goods. Usually quantity is in pallets, cartons, pieces, packages, boxes, etc. Please prioritize the packaging types based on their size, as follows: Pallets >> Cartons >> Pieces. Larger packaging types will have a lower count."}
+  },
+  "required": []
+}

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

@@ -2,7 +2,7 @@ Task: You are a document entity extraction specialist. Given a document, your ta
 
 Extract all the data points from the given document.
 Each data point is part of a master field called "skuData". There may be multiple sku entries in a document.
-Your goal is to extract all instances.
+Your task is to extract the text value of the following entities and their page numbers starting from 0 where the value was found in the document:
 
 Instructions:
 - Populate fields as defined in the response schema.