📄️ SummarizedExtraction Introduction
In Prompt Studio, when you are working on field extractions, it's way easier for you to think of one prompt as something used for extracting one field, or a group of closely related fields (like the individual items in a line item) from a document. This also means that you can tweak a prompt to make it better without having to worry about it affecting the quality of other prompts. This one to one relationship between a prompt and a field is a design feature of Prompt Studio that makes long-term maintenance of projects with dozens of complex extractions easier.
📄️ Developing and verifying SummarizedExtraction
When developing your prompts in Prompt Studio, you can enable SummarizedExtraction and see how it affects your extractions. Of course, in Prompt Studio, you're only developing prompts and defining the extraction schema. Ultimately, SummarizedExtraction runs as part of a deployed Prompt Studio project as one of the following integration types:
📄️ Deploying SummarizedExtraction
We discussed earlier in Developing and verifying SummarizedExtraction that while in Prompt Studio, you're only verifying if SummarizedExtraction is doing a good job of the required structured extraction. SummarizedExtraction needs to be deployed as part of API Deployments, ETL Pipelines, Human Quality Review or Task Pipelines workflow. In this section, let's see how, when deploying one of the previously mentioned types of workflows, we can enable SummarizedExtraction.