You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/content-understanding/tutorial/RAG-tutorial.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -173,11 +173,11 @@ for analyzer in analyzer_configs:
173
173
174
174
**Note:** Field extraction schemas are optional and not required for performing content extraction. To execute content extraction and create analyzers without defining field schemas, simply provide the analyzer ID and the file to be analyzed.
175
175
176
-
**Here is a sample schema definition:**
176
+
Schemas were used in this tutorial. Here is an example of a schema definition
177
177
178
178
# [Document](#tab/document)
179
179
180
-
To create a custom analyzer, you need to define a field schema that describes the structured data you want to extract. In the following example, we define a schema for extracting basic information from an invoice document.
180
+
In the following example, we define a schema for extracting basic information from an invoice document.
181
181
182
182
```json
183
183
{
@@ -219,7 +219,7 @@ To create a custom analyzer, you need to define a field schema that describes th
219
219
220
220
# [Image](#tab/image)
221
221
222
-
To create a custom analyzer, you need to define a field schema that describes the structured data you want to extract. In the following example, we define a schema for identifying chart types in an image.
222
+
In the following example, we define a schema for identifying chart types in an image.
223
223
224
224
225
225
```json
@@ -243,7 +243,7 @@ To create a custom analyzer, you need to define a field schema that describes th
243
243
244
244
# [Audio](#tab/audio)
245
245
246
-
To create a custom analyzer, you need to define a field schema that describes the structured data you want to extract. In the following example, we define a schema for extracting basic information from call transcripts.
246
+
In the following example, we define a schema for extracting basic information from call transcripts.
247
247
248
248
```json
249
249
{
@@ -282,7 +282,7 @@ To create a custom analyzer, you need to define a field schema that describes th
282
282
283
283
# [Video](#tab/video)
284
284
285
-
To create a custom analyzer, you need to define a field schema that describes the structured data you want to extract. In the following example, we define a schema for extracting basic information from marketing videos.
285
+
In the following example, we define a schema for extracting basic information from marketing videos.
286
286
287
287
```json
288
288
{
@@ -307,7 +307,7 @@ To create a custom analyzer, you need to define a field schema that describes th
307
307
---
308
308
309
309
## Perform Content and Field Analysis
310
-
**Content extraction** is the first step in the RAG implementation process. It transforms raw multimodal data—such as documents, images, audio, and video—into structured, searchable formats. This foundational step ensures that the content is organized and ready for indexing and retrieval. Content extraction provides the baseline for indexing and retrieval but may not fully address domain-specific needs or provide deeper contextual insights.
310
+
**Content extraction** is the first step in the RAG implementation process. It transforms raw multimodal datainto structured, searchable formats. This foundational step ensures that the content is organized and ready for indexing and retrieval. While content extraction provides the baseline for indexing and retrieval it may not fully address domain-specific needs or provide deeper contextual insights.
311
311
[Learn more]() about content extraction capabilities for each modality.
312
312
313
313
**Field extraction** builds on content extraction by using AI to generate additional metadata that enriches the knowledge base. This step allows you to define custom fields tailored to your specific use case, enabling more precise retrieval and enhanced search relevance. Field extraction complements content extraction by adding depth and context, making the data more actionable for RAG scenarios.
0 commit comments