new assesment

Author: kazmer97

config_library/pattern-2/bank-statement-sample/config.yaml

@@ -404,11 +404,7 @@ assessment:
   image:
     target_height: ""
     target_width: ""
-  granular:
-    enabled: true
-    max_workers: "20"
-    simple_batch_size: "3"
-    list_batch_size: "1"
+  max_workers: "20"
   default_confidence_threshold: "0.8"
   top_p: "0.1"
   max_tokens: "10000"
@@ -461,12 +457,15 @@ assessment:
     - page: Page number where the field appears (starting from 1)
 
     Coordinate system:
+    - The document images have ruler markings along all edges showing the 0-1000 coordinate scale
+    - Use these ruler markings to determine precise coordinates for bounding boxes
     - Use normalized scale 0-1000 for both x and y axes
     - x1, y1 = top-left corner of bounding box  
     - x2, y2 = bottom-right corner of bounding box
     - Ensure x2 > x1 and y2 > y1
     - Make bounding boxes tight around the actual text content
     - If a field spans multiple lines, create a bounding box that encompasses all relevant text
+    - Reference the ruler markings on the image edges to provide accurate coordinates
     </spatial-localization-guidelines>
 
     <final-instructions>
@@ -528,6 +527,9 @@ assessment:
     }
 
     IMPORTANT:  
+    - The <task-schema> contains raw JSON schema for the attributes you should assess
+    - The <extraction-results> contains the FULL extraction data (you have complete context for cross-referencing)
+    - The <task-instruction> specifies which attributes to focus on
     - For LIST attributes like "Transactions", assess EACH individual item in the list separately with individual bounding boxes
     - Each transaction should be assessed as a separate object in the array with its own spatial coordinates
     - Do NOT provide aggregate assessments for list items - assess each one individually with precise locations
@@ -548,9 +550,13 @@ assessment:
 
     <<CACHEPOINT>>
 
-    <attributes-definitions>
-    {ATTRIBUTE_NAMES_AND_DESCRIPTIONS}
-    </attributes-definitions>
+    <task-schema>
+    {TASK_SCHEMA}
+    </task-schema>
+
+    <task-instruction>
+    {TASK_INSTRUCTION}
+    </task-instruction>
 
     <extraction-results>
     {EXTRACTION_RESULTS}

config_library/pattern-2/lending-package-sample/config.yaml

@@ -10,6 +10,7 @@ ocr:
     - name: LAYOUT
     - name: TABLES
     - name: SIGNATURES
+  max_workers: "20"
   image:
     target_width: ""
     target_height: ""
@@ -1188,6 +1189,7 @@ classes:
 classification:
   classificationMethod: multimodalPageLevelClassification
   maxPagesForClassification: "ALL"
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
@@ -1252,6 +1254,7 @@ extraction:
   agentic:
     enabled: false
     review_agent: false
+  max_workers: "20"
   image:
     target_width: ""
     target_height: ""
@@ -1425,14 +1428,10 @@ summarization:
 assessment:
   enabled: true
   validation_enabled: false
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
-  granular:
-    enabled: true
-    max_workers: "20"
-    simple_batch_size: "3"
-    list_batch_size: "1"
   default_confidence_threshold: "0.8"
   top_p: "0.1"
   max_tokens: "10000"
@@ -1485,12 +1484,15 @@ assessment:
     - page: Page number where the field appears (starting from 1)
 
     Coordinate system:
+    - The document images have ruler markings along all edges showing the 0-1000 coordinate scale
+    - Use these ruler markings to determine precise coordinates for bounding boxes
     - Use normalized scale 0-1000 for both x and y axes
     - x1, y1 = top-left corner of bounding box  
     - x2, y2 = bottom-right corner of bounding box
     - Ensure x2 > x1 and y2 > y1
     - Make bounding boxes tight around the actual text content
     - If a field spans multiple lines, create a bounding box that encompasses all relevant text
+    - Reference the ruler markings on the image edges to provide accurate coordinates
     </spatial-localization-guidelines>
 
     <final-instructions>
@@ -1552,6 +1554,9 @@ assessment:
     }
 
     IMPORTANT:  
+    - The <task-schema> contains raw JSON schema for the attributes you should assess
+    - The <extraction-results> contains the FULL extraction data (you have complete context for cross-referencing)
+    - The <task-instruction> specifies which attributes to focus on
     - For LIST attributes like "Transactions", assess EACH individual item in the list separately with individual bounding boxes
     - Each transaction should be assessed as a separate object in the array with its own spatial coordinates
     - Do NOT provide aggregate assessments for list items - assess each one individually with precise locations
@@ -1572,9 +1577,13 @@ assessment:
 
     <<CACHEPOINT>>
 
-    <attributes-definitions>
-    {ATTRIBUTE_NAMES_AND_DESCRIPTIONS}
-    </attributes-definitions>
+    <task-schema>
+    {TASK_SCHEMA}
+    </task-schema>
+
+    <task-instruction>
+    {TASK_INSTRUCTION}
+    </task-instruction>
 
     <extraction-results>
     {EXTRACTION_RESULTS}

config_library/pattern-2/rvl-cdip-package-sample-with-few-shot-examples/config.yaml

@@ -11,6 +11,7 @@ ocr:
     - name: LAYOUT
     - name: TABLES
     - name: SIGNATURES
+  max_workers: "20"
   image:
     dpi: "150"
     target_width: ""
@@ -809,6 +810,7 @@ classes:
 
 classification:
   maxPagesForClassification: "ALL"
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
@@ -863,6 +865,7 @@ classification:
     5. Outputting in the exact JSON format specified in <output-format>
     </final-instructions>
 extraction:
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
@@ -963,14 +966,10 @@ extraction:
 assessment:
   enabled: true
   validation_enabled: false
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
-  granular:
-    enabled: true
-    max_workers: "20"
-    simple_batch_size: "3"
-    list_batch_size: "1"
   default_confidence_threshold: "0.8"
   top_p: "0.1"
   max_tokens: "10000"
@@ -1023,12 +1022,15 @@ assessment:
     - page: Page number where the field appears (starting from 1)
 
     Coordinate system:
+    - The document images have ruler markings along all edges showing the 0-1000 coordinate scale
+    - Use these ruler markings to determine precise coordinates for bounding boxes
     - Use normalized scale 0-1000 for both x and y axes
     - x1, y1 = top-left corner of bounding box  
     - x2, y2 = bottom-right corner of bounding box
     - Ensure x2 > x1 and y2 > y1
     - Make bounding boxes tight around the actual text content
     - If a field spans multiple lines, create a bounding box that encompasses all relevant text
+    - Reference the ruler markings on the image edges to provide accurate coordinates
     </spatial-localization-guidelines>
 
     <final-instructions>
@@ -1090,6 +1092,9 @@ assessment:
     }
 
     IMPORTANT:  
+    - The <task-schema> contains raw JSON schema for the attributes you should assess
+    - The <extraction-results> contains the FULL extraction data (you have complete context for cross-referencing)
+    - The <task-instruction> specifies which attributes to focus on
     - For LIST attributes like "Transactions", assess EACH individual item in the list separately with individual bounding boxes
     - Each transaction should be assessed as a separate object in the array with its own spatial coordinates
     - Do NOT provide aggregate assessments for list items - assess each one individually with precise locations
@@ -1110,9 +1115,13 @@ assessment:
 
     <<CACHEPOINT>>
 
-    <attributes-definitions>
-    {ATTRIBUTE_NAMES_AND_DESCRIPTIONS}
-    </attributes-definitions>
+    <task-schema>
+    {TASK_SCHEMA}
+    </task-schema>
+
+    <task-instruction>
+    {TASK_INSTRUCTION}
+    </task-instruction>
 
     <extraction-results>
     {EXTRACTION_RESULTS}

config_library/pattern-2/rvl-cdip-package-sample/config.yaml

@@ -10,6 +10,7 @@ ocr:
     - name: LAYOUT
     - name: TABLES
     - name: SIGNATURES
+  max_workers: "20"
   image:
     dpi: "150"
     target_width: ""
@@ -764,6 +765,7 @@ classes:
           labeled 'notes', 'remarks', or 'comments'.
 classification:
   maxPagesForClassification: "ALL"
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
@@ -906,6 +908,7 @@ classification:
     You are a document classification expert who can analyze and classify multiple documents and their page boundaries within a document package from various domains. Your task is to determine the document type based on its content and structure, using the provided document type definitions. Your output must be valid JSON according to the requested format.
   classificationMethod: textbasedHolisticClassification
 extraction:
+  max_workers: "20"
   image:
     target_width: ""
     target_height: ""
@@ -1067,14 +1070,10 @@ summarization:
 assessment:
   enabled: true
   validation_enabled: false
+  max_workers: "20"
   image:
     target_height: ""
     target_width: ""
-  granular:
-    enabled: true
-    max_workers: "20"
-    simple_batch_size: "3"
-    list_batch_size: "1"
   default_confidence_threshold: "0.8"
   top_p: "0.1"
   max_tokens: "10000"
@@ -1127,12 +1126,15 @@ assessment:
     - page: Page number where the field appears (starting from 1)
 
     Coordinate system:
+    - The document images have ruler markings along all edges showing the 0-1000 coordinate scale
+    - Use these ruler markings to determine precise coordinates for bounding boxes
     - Use normalized scale 0-1000 for both x and y axes
     - x1, y1 = top-left corner of bounding box  
     - x2, y2 = bottom-right corner of bounding box
     - Ensure x2 > x1 and y2 > y1
     - Make bounding boxes tight around the actual text content
     - If a field spans multiple lines, create a bounding box that encompasses all relevant text
+    - Reference the ruler markings on the image edges to provide accurate coordinates
     </spatial-localization-guidelines>
 
     <final-instructions>
@@ -1194,6 +1196,9 @@ assessment:
     }
 
     IMPORTANT:  
+    - The <task-schema> contains raw JSON schema for the attributes you should assess
+    - The <extraction-results> contains the FULL extraction data (you have complete context for cross-referencing)
+    - The <task-instruction> specifies which attributes to focus on
     - For LIST attributes like "Transactions", assess EACH individual item in the list separately with individual bounding boxes
     - Each transaction should be assessed as a separate object in the array with its own spatial coordinates
     - Do NOT provide aggregate assessments for list items - assess each one individually with precise locations
@@ -1214,9 +1219,13 @@ assessment:
 
     <<CACHEPOINT>>
 
-    <attributes-definitions>
-    {ATTRIBUTE_NAMES_AND_DESCRIPTIONS}
-    </attributes-definitions>
+    <task-schema>
+    {TASK_SCHEMA}
+    </task-schema>
+
+    <task-instruction>
+    {TASK_INSTRUCTION}
+    </task-instruction>
 
     <extraction-results>
     {EXTRACTION_RESULTS}