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/concepts/standard-pro-modes.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ Not sure which mode is right for your scenario? The following charts compare sta
75
75
| Scenario | Standard mode | Pro mode|
76
76
|----|----|----|
77
77
|**Invoice analysis**| Extract insights on invoice data at scale and enable RAG search and further data analysis and visualization. Answer questions like: <br> • Extract purchase order number, total, due date, and line items for entry into database. | Analyze invoices and contractual agreements with clients and apply multi-step reasoning to draw conclusions on that data. Answer questions like: <br> • Does this invoice fulfill the contractual agreement we have in place with this client? <br> • Does this invoice need further review? |
78
-
|**Call center transcript analytics**| Extract insights on large volumes of call center data to gain valuable insights on sentiment, understand customer issues, and create targeted training to address major pain points. Answer questions like: <br> • What are the main issues customers are calling about? <br> • What is the average length of calls made about x issue? | Analyze call center transcript data and apply multi-step reasoning to understand how call center employees are addressing customer needs, and if they're following guidelines. Answer questions like: <br> • Did the call center employee introduce themselves? <br> • Did this answer "pass" certain criteria? |
78
+
|**Call center transcript analytics**| Extract insights on large volumes of call center data to gain valuable insights on sentiment, understand customer issues, and create targeted training to address major pain points. Answer questions like: <br> • What are the main issues customers are calling about? <br> • What is the average length of calls made about x issue? | Analyze call center transcript data and apply multi-step reasoning to understand how call center employees are addressing customer needs, and if they're following guidelines. Answer questions like: <br> • Did the call center employee introduce themselves? <br> • Did this answer *pass* certain criteria? |
79
79
|**Mortgage application processing**| Extract the key values from mortgage application data and make it searchable and more easily accessible. Answer questions like: <br> • What year was the mortgage application submitted? <br> • What are the names on the application? | Analyze supplementary supporting documentation and mortgage applications to determine whether a prospective home buyer provides all the necessary documentation to secure a mortgage. Answer questions like: <br> • Do the names and social security numbers on the mortgage application match the supporting documentation? |
80
80
81
81
## Try pro mode
@@ -85,10 +85,16 @@ You can try out the features of both Content Understanding standard and pro mode
85
85
### Pro mode known limitations and best practices
86
86
87
87
* Content Understanding pro mode currently doesn't offer confidence scores or grounding. It currently supports generative and classification of your fields but doesn't support extraction only.
88
+
88
89
* Content Understanding pro mode is currently only available for documents.
89
-
* The system works in “lookup mode” on reference documents: don’t expect exhaustive information recovery; if this is desired, include the document in your input documents instead.
90
-
* Be as specific as possible with your schema (e.g., rather than identifying a list of inconsistencies, create a list field for each inconsistency type and describe it), and if possible, reference which parts of which documents should be consulted.
91
-
* Keep reference documents short and sweet: Limit documents to the critical ones, and keep them short where possible to improve recall.
90
+
91
+
* The system operates in *lookup mode* when referencing documents. As a result, comprehensive information retrieval shouldn't be expected. If exhaustive recovery of data is required, we recommend that you incorporate the document into the input set.
92
+
93
+
* Schemas should be designed with the highest level of specificity possible. For instance, instead of presenting a generalized list of inconsistencies, it's advisable to create distinct fields for each type of inconsistency, accompanied by detailed descriptions. Additionally, wherever feasible, references to specific sections of relevant documents that should be reviewed should be included.
94
+
95
+
* Reference documents should be concise and focused. Prioritize essential documents and ensure they're as brief as possible to enhance retention and recall.
0 commit comments