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: learn-pr/wwl-data-ai/create-question-answer-solution-ai-language/includes/6-test-publish-knowledge-base.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,8 @@ After you have defined a knowledge base, you can train its natural language mode
5
5
6
6
You can test your knowledge base interactively in Language Studio, submitting questions and reviewing the answers that are returned. You can inspect the results to view their confidence scores as well as other potential answers.
7
7
8
-
:::image type="content" source="../media/test-new-small.png" alt-text="Screenshot of the test pane of the custom question answering project in the Language studio."lightbox="../media/test-new.png":::
8
+
:::image type="content" source="../media/test-new-small.png" alt-text="Screenshot of the test pane of the custom question answering project in the Language studio.":::
9
9
10
10
## Deploying a knowledge base
11
11
12
-
When you are happy with the performance of your knowledge base, you can deploy it to a REST endpoint that client applications can use to submit questions and receive answers. You can deploy it directly from Language Studio.
12
+
When you're happy with the performance of your knowledge base, you can deploy it to a REST endpoint that client applications can use to submit questions and receive answers. You can deploy it directly from Language Studio.
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/plan-form-recognizer-solution/includes/2-understand.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ The other prebuilt models expect a common type of form or document, such as:
48
48
- Health insurance card
49
49
50
50
> [!IMPORTANT]
51
-
> This list shows a subset of the prebuilt models available. Check the Azure AI Document Intelligence documentation for [all available models](/azure/ai-services/document-intelligence/model-overview?view=doc-intel-4.0.0&azure-portal=true#model-overview).
51
+
> This list shows a subset of the prebuilt models available. Check the Azure AI Document Intelligence documentation for [all available models](/azure/ai-services/document-intelligence/model-overview?azure-portal=true#model-overview).
52
52
53
53
If you have an unusual or unique type of form, you can use the above general document analysis prebuilt models to extract information from them. However, if you want to extract more specific information than the prebuilt models support, you can create a **custom model** and train it by using examples of completed forms.
Copy file name to clipboardExpand all lines: learn-pr/wwl-data-ai/plan-form-recognizer-solution/includes/4-choose-model-type.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ In this unit, you'll learn about the prebuilt models available in Azure AI Docum
6
6
7
7
## Prebuilt models
8
8
9
-
Document types such as invoices and receipts vary in different businesses and industry but have similar structures and key-value pairs. For example, a "Total cost" value is likely to appear on almost all invoices although it might be called "Total", "Sum", or some other name. Microsoft has provided a set of prebuilt models with Azure AI Document Intelligence to handle the most common types of documents. You don't have to train these models and you can create solutions using them very quickly.
9
+
Document types such as invoices and receipts vary in different businesses and industry but have similar structures and key-value pairs. For example, a "Total cost" value is likely to appear on almost all invoices although it might be called "Total", "Sum", or some other name. Azure AI Document Intelligence provides a set of prebuilt models to handle the most common types of documents. You don't have to train these models and you can create solutions using them quickly.
10
10
11
11
### General document analysis models
12
12
@@ -50,9 +50,9 @@ The other prebuilt models are each designed to handle, and trained on, a specifi
50
50
51
51
## Custom models
52
52
53
-
If the prebuilt models don't suit your purposes, you can create a custom model and train it to analyze the specific type of document users will send to your Azure AI Document Intelligence service. The general document analyzer prebuilt models can extract rich information from these forms and you might be able to use them if your requirements are to obtain general data. However, by using a custom model, trained on forms with similar structures and key-value pairs, you will obtain more predictable and standardized results from your unusual form types.
53
+
If the prebuilt models don't suit your purposes, you can create a custom model and train it to analyze the specific type of document users will send to your Azure AI Document Intelligence service. The general document analyzer prebuilt models can extract rich information from these forms and you might be able to use them if your requirements are to obtain general data. However, by using a custom model, trained on forms with similar structures and key-value pairs, you'll obtain more predictable and standardized results from your unusual form types.
54
54
55
-
To train a custom model, you must supply at least five examples of the completed form but the more examples you supply, the greater the confidence levels Azure AI Document Intelligence will return when it analyzes input. The more varied your documents are in terms of structure and terminology, the greater the number of example documents you will need to supply to train a reliable model. You can either supply a labeled dataset to describe the expected data or allow the model to identify key-value pairs and table data based on what it finds in the example forms. Also, make sure your training forms include examples that span the full range of possible input. For example, if you are expecting both hand-written and printed entries, include them both in your training.
55
+
To train a custom model, you must supply at least five examples of the completed form but the more examples you supply, the greater the confidence levels Azure AI Document Intelligence will return when it analyzes input. The more varied your documents are in terms of structure and terminology, the greater the number of example documents you'll need to supply to train a reliable model. You can either supply a labeled dataset to describe the expected data or allow the model to identify key-value pairs and table data based on what it finds in the example forms. Also, make sure your training forms include examples that span the full range of possible input. For example, if you're expecting both hand-written and printed entries, include them both in your training.
56
56
57
57
Once you have trained a custom model in this way, Azure AI Document Intelligence can accurately and predictably identify information in your unique forms.
58
58
@@ -65,7 +65,7 @@ There are two kinds of custom model:
65
65
66
66
## Composed models
67
67
68
-
A composed model is one that consists of multiple custom models. Typical scenarios where composed models help are when you don't know the submitted document type and want to classify and then analyze it. They are also useful if you have multiple variations of a form, each with a trained individual model. When a user submits a form to the composed model, Document Intelligence automatically classifies it to determine which of the custom models should be used in its analysis. In this approach, a user doesn't have to know what kind of document it is before submission. That can be helpful when you're using lots of similar forms or when you want to publish a single endpoint for all your form types.
68
+
A composed model is one that consists of multiple custom models. Typical scenarios where composed models help are when you don't know the submitted document type and want to classify and then analyze it. They're also useful if you have multiple variations of a form, each with a trained individual model. When a user submits a form to the composed model, Document Intelligence automatically classifies it to determine which of the custom models should be used in its analysis. In this approach, a user doesn't have to know what kind of document it is before submission. That can be helpful when you're using lots of similar forms or when you want to publish a single endpoint for all your form types.
69
69
70
70
> [!IMPORTANT]
71
71
> The results from a composed model include the `docType` property, which indicates the custom model that was chosen to analyze each form.
0 commit comments