Skip to content

Commit 0d4b8aa

Browse files
Merge branch 'main' into shikhar-cyber
2 parents 8f4a1e5 + c69057d commit 0d4b8aa

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

examples/partners/model_selection_guide/model_selection_guide.ipynb

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,9 @@
6161
"\n",
6262
"### OpenAI Model Evolution \n",
6363
"\n",
64+
6465
"![OpenAI Model Evolution](../../../images/2.2_model_evolution.png)\n",
66+
6567
"\n",
6668
"### Key Characteristics\n",
6769
"\n",
@@ -79,7 +81,9 @@
7981
"\n",
8082
"## 3A. Use Case: Long-Context RAG for Legal Q&A\n",
8183
"\n",
84+
8285
"![Long-Context RAG for Legal Q&A](../../../images/3A_rag_task_card.png)\n",
86+
8387
"## 🗂️ TL;DR Matrix\n",
8488
"\n",
8589
"This table summarizes the core technology choices and their rationale for **this specific Long-Context Agentic RAG implementation**.\n",
@@ -133,7 +137,9 @@
133137
"id": "db9bad1b",
134138
"metadata": {},
135139
"source": [
140+
136141
"![Hierarchical Router](../../../images/3A_rag_hierarchical_router.png)\n",
142+
137143
"\n",
138144
"\n",
139145
"## Agentic RAG System: Model Usage\n",
@@ -1815,7 +1821,9 @@
18151821
"================================================================================\n",
18161822
"\n",
18171823
"## 3B. Use Case: AI Co-Scientist for Pharma R&D\n",
1824+
18181825
"![AI Co-Scientist for Pharma R&D](../../../images/3B_reasoning_task_card.png)\n",
1826+
18191827
"\n",
18201828
"This section details how to build an AI system that functions as a \"co-scientist\" to accelerate experimental design in pharmaceutical R&D, focusing on optimizing a drug synthesis process under specific constraints.\n",
18211829
"\n",
@@ -1855,7 +1863,9 @@
18551863
"\n",
18561864
"The system employs a multi-agent architecture that emulates a high-performing scientific team. Different AI components, acting in specialized roles (such as ideation, critique, and learning from outcomes), collaborate using various models and tools to execute the workflow.\n",
18571865
"\n",
1866+
18581867
"![AI Co-Scientist Architecture](../../../images/3B_coscientist_architecture.png)\n",
1868+
18591869
"\n",
18601870
"### 2.1. **Scientist Input & Constraints:** \n",
18611871
"The process starts with the scientist defining the goal, target compound, and constraints."
@@ -2463,7 +2473,9 @@
24632473
"\n",
24642474
"## 3C. Use Case: Insurance Claim Processing\n",
24652475
"\n",
2476+
24662477
"![](../../../images/3C_insurance_task_card.png)\n",
2478+
24672479
"\n",
24682480
"Many businesses are faced with the task of digitizing hand filled forms. In this section, we will demonstrate how OpenAI can be used to digitize and validate a hand filled insurance form. While this is a common problem for insurance, the same techniques can be applied to a variety of other industries and forms, for example tax forms, invoices, and more.\n",
24692481
"\n",
@@ -2493,7 +2505,9 @@
24932505
"\n",
24942506
"The high level basic architecture of the solution is shown below.\n",
24952507
"\n",
2508+
24962509
"![](../../../images/3C_insurance_architecture.png)\n",
2510+
24972511
"\n",
24982512
"This task is complex and requires a wide variety of model capabilities, including vision, function calling, reasoning, and structured output. While `o3` is capable of doing all of these at once, we found during experimentation that `o4-mini` alone was not sufficient to achieve the necessary performance. Due to the higher relative costs of `o3`, we instead opted for a two-stage approach.\n",
24992513
"\n",
@@ -2503,7 +2517,9 @@
25032517
"\n",
25042518
"To demonstrate concretely how this works, let's look at a sample image of an insurance form.\n",
25052519
"\n",
2520+
25062521
"![](../../../images/3C_insurance_form.png)\n",
2522+
25072523
"\n",
25082524
"While the form itself is fairly straightforward, there is missing data and ambiguous information that will be difficult for a traditional OCR system to fill out correctly. First, notice that the zip code and county have been omitted. Second, the email address of the user is ambiguous \\-- it could be `[email protected]` or `[email protected]`. In the following sections, we will walk through how a well-designed solution can handle these ambiguities and return the correct form results.\n",
25092525
"\n",
@@ -3186,7 +3202,10 @@
31863202
"\n",
31873203
"## Adaptation Decision Tree\n",
31883204
"\n",
3205+
31893206
"![Model Selection Decision Tree](../../../images/3D_model_selection_flowchart.png)\n",
3207+
3208+
31903209
"\n",
31913210
"## Communicating Model Selection to Non-Technical Stakeholders\n",
31923211
"\n",
@@ -3286,10 +3305,12 @@
32863305
"\n",
32873306
"## Contributors\n",
32883307
"\n",
3308+
32893309
"- [Kashyap Coimbatore Murali](https://www.linkedin.com/in/kashyap-murali/)\n",
32903310
"- [Nate Harada](https://www.linkedin.com/in/nate-harada/) \n",
32913311
"- [Sai Prashanth Soundararaj](https://www.linkedin.com/in/saiprashanths/)\n",
32923312
"- [Shikhar Kwatra](https://www.linkedin.com/in/shikharkwatra/)"
3313+
32933314
]
32943315
}
32953316
],

0 commit comments

Comments
 (0)