data-science-document-ai 1.59.0__tar.gz → 1.60.1__tar.gz

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/PKG-INFO

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

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "data-science-document-ai"
-version = "1.59.0"
+version = "1.60.1"
 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.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/evergreen/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,7 +21,7 @@
       "nullable": true,
       "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. E.g., FULL RETURN TO or Export terminal name."
     },
-    "performaDate": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
       "description": "The date considered to apply the rates and charges specified in the booking confirmation"
@@ -34,7 +34,7 @@
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Booking Number'."
     },
     "mblNumber": {
       "type": "STRING",
@@ -139,7 +139,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document e,g, Evergreen Line."
+      "description": "The name of the carrier who issued the document. Extract full name. e,g, Evergreen Line."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/evergreen/prompt.txt

@@ -17,6 +17,12 @@ For Import Shipment: The loaded container / cargo arrives at a port of discharge
 - Populate fields as defined in the response schema.
 - Use the data field description to understand the context of the data.
 
+- Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".
+    - containerType: The type of container (e.g., 20FT, 40FT, 20ft, 40ft, 40HC, 20DC, etc...).
+    - pickupDepotCode: The code of the depot where the empty container is picked up.It is identified as Empty Pick Up AT Depot or Export Empty Pick Up Depot(s).
+    - dropOffDepotCode: The code of the depot where the empty container is dropped off. It is identified as Import Empty Drop Off Depot(s). Full Return To is not the drop off depot.
+
+
 - transportLegs: Multiple Transport Legs entries may exist, capture all instances under "transportLegs". Make sure the order of the legs are important.
     - eta: The estimated time of arrival for a specific leg.
     - etd: The estimated time of departure for a specific leg. ETD DATE above the PORT OF DISCHARGING information.

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/hapag-lloyd/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It can be mentioned as Contract No., Contract Reference, or Quotation No. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,10 +21,10 @@
       "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": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
-      "description": "The date considered to apply the rates and charges specified in the booking confirmation"
+      "description": "The date considered to apply the rates and charges specified in the booking confirmation. Issue date is not a Proforma Date."
     },
     "cyCutOff": {
       "type": "STRING",
@@ -34,7 +34,7 @@
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Booking Number'."
     },
     "mblNumber": {
       "type": "STRING",
@@ -139,7 +139,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document e,g, Hapag-Lloyd."
+      "description": "The name of the carrier who issued the document. Extract full name e,g, Hapag-Lloyd (Vietnam) Ltd."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/hapag-lloyd/prompt.txt

@@ -28,10 +28,10 @@ For Import Shipment: The loaded container / cargo arrives at a port of discharge
 - 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.
+    - Extract the full name and address of the carrier who is the main parent company in the document.
     - It can be found in the top section of the document, often near the logo or header.
     - Example:
-        - "Hapag-Lloyd" for carrierName
+        - "Hapag-Lloyd" or "Hapag-Lloyd (China) LTD" for carrierName
         - Hamburg, Germany, Poland, Italy, Vietnam, China etc... for carrierAddress
 
 - transportLegs: Multiple Transport Legs entries may exist, capture all instances under "transportLegs". Make sure the order of the legs are important.

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/maersk/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,10 +21,10 @@
       "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 Return Equip Delivery Terminal."
     },
-    "performaDate": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
-      "description": "The date considered to apply the rates and charges specified in the booking confirmation. It is mentioned as Price Calculation Date or Performa Date."
+      "description": "The date considered to apply the rates and charges specified in the booking confirmation. It is mentioned as Price Calculation Date or proforma Date. Release Date, ETD, and ETA is not considered as proforma Date."
     },
     "cyCutOff": {
       "type": "STRING",
@@ -34,12 +34,12 @@
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Booking Number'."
     },
     "mblNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "Bill of Lading number (B/L NO.), a document issued by the carrier."
+      "description": "Master Bill of Lading number (B/L NO.), a document issued by the carrier. Commonly known as 'Bill of Lading Number', 'SEA WAYBILL', 'BILL OF LADING NO.', 'BL Number', 'BL No.', 'B/L No.', 'BL-Nr.', 'B/L', or 'HBL No.'"
     },
     "pickUpReference": {
       "type": "STRING",
@@ -74,7 +74,7 @@
           "dropOffDepotCode": {
             "type": "STRING",
             "nullable": true,
-            "description": "The depot code where the empty container will be dropped off."
+            "description": "The depot code where the empty container will be dropped off. Return Equip Delivery Terminal and Full Return Location is not the dropOffDepotCode."
           }
         }
       },
@@ -139,7 +139,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document e,g, MAERSK."
+      "description": "The name of the carrier who issued the document. Extract the full  name. e,g, MAERSK."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/maersk/prompt.txt

@@ -24,18 +24,19 @@ For Import Shipment: The loaded container / cargo arrives at a port of discharge
 - cyCutOff: The deadline for cargo to be delivered to the Container Yard. It can be referred to as Cargo Cut-off deadline, FCL delivery cut-off, CY CUT OFF, CY Closing - Latest Return Container Date.
 - 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
+- Haulage Instructions Closing date in the second page is a cyCutOff but not siCutOff or vgmCutOff.
 
 - carrierName and carrierAddress:
-    - Extract the name and address of the carrier who is the main parent company in the document.
+    - Extract the full name and address of the carrier who is the main parent company in the document.
     - It can be found in the top section of the document, often near the logo or header.
     - Example:
-        - "MAERSK" for carrierName
+        - "MAERSK" or "MAERSK Poland" for carrierName
         - Hamburg, Germany, NETHERLANDS, Poland, Italy, Vietnam, China SHANGHAI BRANCH etc... for carrierAddress
 
 - Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".
     - 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. Can be found as Empty Container Depot under Load Itinerary table.
-    - dropOffDepotCode: The code of the depot where the empty container is dropped off.
+    - dropOffDepotCode: The code of the depot where the empty container is dropped off. Return Equip Delivery Terminal and Full Return Location is not the dropOffDepotCode.
 
 - 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.

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/msc/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It can be found as Service Contract/Rate Reff. No."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It can be found as Service Contract/Rate Reff. No. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,10 +21,10 @@
       "nullable": true,
       "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. It can be found as GATE IN AT TERMINAL/DEPOT"
     },
-    "performaDate": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
-      "description": "The date considered to apply the rates and charges specified in the booking confirmation. It is mentioned as Price Calculation Date or Performa Date."
+      "description": "The date considered to apply the rates and charges specified in the booking confirmation. It is mentioned as Price Calculation Date or proforma Date."
     },
     "cyCutOff": {
       "type": "STRING",
@@ -34,7 +34,7 @@
     "gateInReference": {
       "type": "STRING",
       "nullable": true,
-      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Our Reference'."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be 'Booking Number'."
     },
     "mblNumber": {
       "type": "STRING",
@@ -69,7 +69,7 @@
           "pickUpDepotCode": {
             "type": "STRING",
             "nullable": true,
-            "description": "The depot code where the empty container will be picked up. It is identified as PICK UP AT DEPOT, Empty Container Depot, or Export Empty Pick Up Depot(s)."
+            "description": "The depot code where the empty container will be picked up. It is identified as PICK UP AT DEPOT, Empty Container Depot, or Export Empty Pick Up Depot(s). Do not extract the address here."
           },
           "dropOffDepotCode": {
             "type": "STRING",
@@ -139,7 +139,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document e,g, MSC."
+      "description": "The name of the carrier who issued the document. Extract full name e,g, MSC or MSC POLAND SP. Z O.O. rather than just MSC."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/msc/prompt.txt

@@ -22,10 +22,10 @@ For Import Shipment: The loaded container / cargo arrives at a port of discharge
 - cyCutOff: The deadline for cargo to be delivered to the Container Yard. It can be found at CUT-OFF(Date/Time), FCL delivery cut-off, CY CUT OFF, CY Closing.
 
 - carrierName and carrierAddress:
-    - Extract the name and address of the carrier who is the main parent company in the document.
+    - Extract the full name and address of the carrier who is the main parent company in the document.
     - It can be found in the top section of the document, often near the logo or header.
     - Example:
-        - "MSC" for carrierName
+        - "MSC" or "MSC POLAND SP. Z O.O." for carrierName
         - Hamburg, Germany, NETHERLANDS, Poland, Italy, Vietnam, China SHANGHAI BRANCH etc... for carrierAddress.
 
 - Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/oocl/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It can be referred as Rate Agreement Number or Contract No."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It can be referred as Rate Agreement Number or Contract No.. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,12 +21,7 @@
       "nullable": true,
       "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. E.g., FULL RETURN LOCATION"
     },
-    "serviceCode": {
-      "type": "STRING",
-      "nullable": true,
-    "description": "The Shipping service code associated with the booking confirmation. It can be found as SERVICE CODE"
-    },
-    "performaDate": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
       "description": "the date considered to apply the rates and charges specified in the booking confirmation"
@@ -114,6 +109,11 @@
             "nullable": true,
             "description": "The International Maritime Organization number for a specific leg. It can be found as IMO No, IMO number."
           },
+          "serviceCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The Shipping service code associated with the booking confirmation. It can be found as SERVICE CODE"
+          },
           "portOfDischarge": {
             "type": "STRING",
             "nullable": true,
@@ -153,7 +153,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document. E.g., OOCL or Orient Overseas Container Line Ltd."
+      "description": "The name of the carrier who issued the document. Extract the full name. E.g., OOCL or Orient Overseas Container Line Ltd."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/other/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG."
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,12 +21,7 @@
       "nullable": true,
       "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. It can be found as Gate In At Terminal, Gate in Terminal, Full Return To Terminal, Full Return Location, Cargo Delivery At, Delivery Terminal, Full Return CY, eyc.."
     },
-    "serviceCode": {
-      "type": "STRING",
-      "nullable": true,
-      "description": "The Shipping service code associated with the booking confirmation. It is often referred to as 'Service Code'"
-    },
-    "performaDate": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
       "description": "the date considered to apply the rates and charges specified in the booking confirmation"
@@ -44,12 +39,12 @@
     "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 load ref., Turn-in reference, or if nothing mentioned, it is booking Number."
+      "description": "A reference code for cargo entering the terminal to drop the loaded cargo for Export. Sometimes it can be load ref., Turn-in reference, or if nothing mentioned, then use booking Number."
     },
     "mblNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "Bill of Lading number (B/L NO.), a document issued by the carrier."
+      "description": "Master Bill of Lading number (B/L NO.), a document issued by the carrier. Commonly known as 'Bill of Lading Number', 'SEA WAYBILL', 'BILL OF LADING NO.', 'BL Number', 'BL No.', 'B/L No.', 'BL-Nr.', 'B/L', or 'HBL No.'"
     },
     "pickUpReference": {
       "type": "STRING",
@@ -114,6 +109,11 @@
             "nullable": true,
             "description": "The International Maritime Organization number for a specific leg. It can be found as IMO No, IMO number."
           },
+          "serviceCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The Shipping service code associated with the booking confirmation. It is often referred to as 'Service Code'"
+          },
           "portOfDischarge": {
             "type": "STRING",
             "nullable": true,
@@ -153,7 +153,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document. E.g,, Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, Evergreen etc."
+      "description": "The name of the carrier who issued the document. E.g,, Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, Evergreen etc. Sometimes, carriers like Shipco, Combitrac uses operating vessels from OOCL or Hapag-Lloyd, so in that case, the carrier name should be the one who issue the document (Shipco Transport (Shanghai) Ltd., Combitrac), not the operating vessel carrier (OOCL, Hapag-Lloyd)."
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/other/prompt.txt

@@ -29,8 +29,10 @@ For Import Shipment: The loaded container / cargo arrives at a port of discharge
 
 - carrierName and carrierAddress:
     - Extract the name and address of the carrier who is the main parent company in the document.
+    - Extract the complete name of the carrier including the entity location such as "Hapag-Lloyd Germany", "MSC Italy", "CMA CGM Vietnam" etc...
+    - Shipco Transport Ltd documents contain carrier: OOCL. Extract the carrier name "Other" but not OOCL.
     - Example:
-        - "Hapag-Lloyd", "MSC", "CMA CGM", "ONE", "COSCO SHIPPING", "Evergreen", "Yang Ming", "ZIM", "PIL", "HMM" etc... for carrierName
+        - "Hapag-Lloyd", "MSC", "CMA CGM", "ONE", "Shipco Transport (Shanghai) Ltd.", "COSCO SHIPPING", "Evergreen", "Yang Ming", "ZIM", "PIL", "HMM" etc... for carrierName
         - Hamburg, Germany, Poland, Italy, Vietnam, China etc... for carrierAddress
 
 - Containers: Need to extract Depot details per Container Type. Multiple Containers entries may exist, capture all instances under "Containers".

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/bookingConfirmation/yangming/placeholders.json

@@ -9,7 +9,7 @@
     "contractNumber": {
       "type": "STRING",
       "nullable": true,
-      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. It is mentioned as SVC-NBR"
+      "description": "It's a contract number between the carrier and Forto Logistics SE & Co KG. Shipment Id 'S' followed by 6, 7, or 8 digits e.g. S9486358 is not a contract number."
     },
     "pickUpTerminalCode": {
       "type": "STRING",
@@ -21,12 +21,7 @@
       "nullable": true,
       "description": "The specific terminal where cargo is gated in especially Export terminal delivery address. It is mentioned as Delivery Terminal."
     },
-    "serviceCode": {
-      "type": "STRING",
-      "nullable": true,
-      "description": "The Shipping service code associated with the booking confirmation."
-    },
-    "performaDate": {
+    "proformaDate": {
       "type": "STRING",
       "nullable": true,
       "description": "the date considered to apply the rates and charges specified in the booking confirmation"
@@ -114,6 +109,11 @@
             "nullable": true,
             "description": "The International Maritime Organization number for a specific leg. It can be found as IMO No, IMO number."
           },
+          "serviceCode": {
+            "type": "STRING",
+            "nullable": true,
+            "description": "The Shipping service code associated with the booking confirmation. It is mentioned as SVC-NBR"
+          },
           "portOfDischarge": {
             "type": "STRING",
             "nullable": true,
@@ -153,7 +153,7 @@
     "carrierName": {
       "type": "STRING",
       "nullable": true,
-      "description": "The name of the carrier who issued the document."
+      "description": "The name of the carrier who issued the document. Extract full name. E.g., Yang Ming Marine Transport Corporation or Yang Ming Shipping EUROPE GmbH"
     }
   },
   "required": ["bookingNumber", "transportLegs", "containers", "cyCutOff", "vgmCutOff", "siCutOff"]

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/customsInvoice/other/placeholders.json

@@ -31,7 +31,7 @@
         },
         "documentType": {"type":  "STRING", "nullable": true},
         "dueDate": {"type":  "STRING", "nullable": true,
-            "description": "The date by which the payment should be made by Forto Logistics SE & Co KG. Do Not calculate dueDate based on issueDate or any other date. Extract it directly from the invoice."},
+            "description": "The date by which the payment should be made by Forto Logistics SE & Co KG. If dueDate is not available in the invoice, calculate dueDate based on issueDate and paymentTerm."},
         "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,

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/customsInvoice/other/prompt.txt

@@ -46,7 +46,11 @@ Your role is to accurately extract specific entities from these invoices to supp
         - CUSTOMS SUPPORT invoices do not have a vatAmount and vatPercentage.
 
 - issueDate: The date the document was issued.
-- dueDate: The date by which the payment should be made. Do Not calculate dueDate based on issueDate or any other date. Extract it directly from the invoice.
+- dueDate:
+    - The date by which the payment should be made. If dueDate is explicitly mentioned in the invoice, extract that value directly.
+    - If dueDate is not available in the invoice, calculate dueDate based on issueDate and paymentTerm.
+    - Example: If issueDate is 01.03.2023 and paymentTerm is 30 days, then dueDate will be 31.03.2023.
+    - If paymentTerm is not available, do not extract dueDate.
 
 - lineItem: Details of each COGS and Customs line item on the invoice from each page. Make sure to extract each amount and currency separately.
     - uniqueId: A unique id which associated with the lineItem as each line item can belong to a different shipment. Extract only if its available in the line item. Either a shipmentId starting with an S and followed by 6 or 8 numeric values or a mblNumber. If shipmentId or mblNumber does not exist, set it to containerNumber.
@@ -91,7 +95,7 @@ Your role is to accurately extract specific entities from these invoices to supp
         - sentence: A sentence from the invoice indicating the payment status (e.g., "Vorschuss", "Prepayment", "Paid", "Partially Paid", "Unpaid"). This helps summarize the overall payment status of the invoice.
 
 IMPORTANT NOTE:
-- Ensure all extracted values are directly from the document. Do not make assumptions or modifications.
+- Ensure all extracted values are directly from the document. Do not make assumptions, modifications or calculations except dueDate.
 - CustomSized invoices contain line items in a table format in a attached page. Table with headings Shipment ID, Partner Line Item Description, Quantity, Amount, and VAT. Extract all the line items from each tables from each page.
 - Do not normalize or modify any entity values.
 - Pay attention to the line item details and paymentInformation, as they may vary significantly across different invoices.

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/partnerInvoice/other/placeholders.json

@@ -29,7 +29,7 @@
         },
         "documentType": {"type": "STRING", "nullable": true},
         "dueDate": {"type": "STRING", "nullable": true,
-            "description": "The date by which the payment should be made by Forto Logistics SE & Co KG. Do Not calculate dueDate based on issueDate or any other date. Extract it directly from the invoice."},
+            "description": "The date by which the payment should be made by Forto Logistics SE & Co KG. If dueDate is not available in the invoice, calculate dueDate based on issueDate and paymentTerm."},
         "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,

{data_science_document_ai-1.59.0 → data_science_document_ai-1.60.1}/src/prompts/library/partnerInvoice/other/prompt.txt

@@ -42,7 +42,11 @@ Your role is to accurately extract specific entities from these invoices to supp
     - Remove "TVA" characters from VAT ID in MSC invoices. For example, CHE-111.954.803 TVA should be extracted as CHE-111.954.803
 
 - issueDate: The date the document was issued.
-- dueDate: The date by which the payment should be made. Do Not calculate dueDate based on issueDate or any other date. Extract it directly from the invoice.
+- dueDate:
+    - The date by which the payment should be made. If dueDate is explicitly mentioned in the invoice, extract that value directly.
+    - If dueDate is not available in the invoice, calculate dueDate based on issueDate and paymentTerm.
+    - Example: If issueDate is 01.03.2023 and paymentTerm is 30 days, then dueDate will be 31.03.2023.
+    - If paymentTerm is not available, do not extract dueDate.
 
 - eta and etd: Few invoices contains same date for ARRIVED/DEPARTED or ETA/ETD. Extract it for both eta and etd.
 
@@ -81,7 +85,7 @@ Your role is to accurately extract specific entities from these invoices to supp
 - reverseChargeSentence: A sentence which indicate that the reverse charge applies. Mostly fund as Tax Clause.
 
 IMPORTANT NOTE:
-- Ensure all extracted values are directly from the document. Do not make assumptions, modifications or calculations.
+- Ensure all extracted values are directly from the document. Do not make assumptions, modifications or calculations except dueDate.
 - CustomSized invoices contain line items in a table format in the attached page. Table with headings Shipment ID, Partner Line Item Description, Quantity, Amount, and VAT. Extract all the line items from such tables from each page.
 - Do not split the quantity into different line items. e.g., if quantity is 2 or 2 CTR or 2 BIL, do not create 2 separate line items with quantity 1 each.
 - Do not normalize or modify any entity values.

data_science_document_ai-1.60.1/src/prompts/library/preprocessing/carrier/prompt.txt

@@ -0,0 +1,5 @@
+You are a person who works for a freight-forwarder company.
+Identify company that provided this DOCUMENT_TYPE_PLACEHOLDER document.
+
+Identify the company only based on the name of the carrier mentioned in the top section of the document in the header, title.
+Extract only if the carrier name is mentioned in the top header of the document. Else, classifiy it as "Other" because few carriers use a different carrier for shipping even though the document is issued by them.

data_science_document_ai-1.59.0/src/prompts/library/preprocessing/carrier/prompt.txt

@@ -1,4 +0,0 @@
-You are a person who works for a freight-forwarder company.
-Identify company that provided this DOCUMENT_TYPE_PLACEHOLDER document.
-
-