add field

Author: chienyuanchang

analyzer_templates/insurance_claims_review_pro_mode.json

@@ -26,6 +26,10 @@
         "description": "VIN of the damaged vehicle. Leave empty if not found.",
         "type": "string"
       },
+      "ReportingOfficer": {
+        "description": "Name of the reporting officer for the incident.",
+        "type": "string"
+      },
       "LineItemCorroboration": {
         "type": "array",
         "description": "Validation of all of the line items on the claim, including parts, services, labors, materials, shipping and other costs and fees. When in doubt about adherence to the policy, mark as suspicious.",

notebooks/field_extraction_pro_mode.ipynb

@@ -421,13 +421,38 @@
     "display(FileLink(output_path))"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "### Let's take a look at the analyze result"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "result_json[\"result\"][\"contents\"][0][\"fields\"]"
+   ]
+  },
   {
    "cell_type": "markdown",
    "metadata": {},
    "source": [
     "### Let's take a deeper look at `LineItemCorroboration` field in the result"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "> We can see that the field `ReportingOfficer` is only available in the car accident report, while fields like `VIN` come solely from the repair estimate document. This shows that information is extracted from both documents to generate a single result. It also illustrates the N:1 relationship between the inputs and the analysis result.  \n",
+    "\n",
+    "> Multiple input documents are combined to produce one unified output. There is always one analysis result, and this is not a batch model where N input documents would yield N outputs."
+   ]
+  },
   {
    "cell_type": "code",
    "execution_count": null,
@@ -442,7 +467,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "> In the LineItemCorroboration field, we see that each line item is extracted with its corresponding information, claim status, and evidence. Items that are not covered by the policy, such as the Starbucks drink and hotel stay, are marked as suspicious, while damage repairs that are supported by the supplied documents in the claim and are permitted by the policy are confirmed."
+    "> In the `LineItemCorroboration` field, we see that each line item, generated from *repair estimate document*, is extracted with its corresponding information, claim status, and evidence. Items that are not covered by the policy, such as the Starbucks drink and hotel stay, are marked as suspicious, while damage repairs that are supported by the supplied documents in the claim and are permitted by the policy are confirmed."
    ]
   },
   {