PE-10 Schema-based structured extraction with an LLM (LLM (large language model) information extraction; form filling from documents)
Fill a fixed set of fields, such as amount, date, party, stated risk or decision, for each document, giving one record per document and the share of missing or not stated values.
What it does
Fills a fixed set of fields, such as amount, date, party, stated risk or decision, for each document. Artefact: one record per document. Read the missing and "not stated" rates and compare a sample with the source.
When to use it
Use when you need the same facts pulled from many reports or filings into one table.
When it does not fit
Fields must be explicit in the text, and inferred fields should be flagged. Validate each task against human labels. No error rates for extraction from filings were found.
Result format
The result is one record per document with the same fixed fields in every record, such as amount, date, party, stated risk or decision. It reports the missing and not stated rate for each field and a sample of records compared with the source text.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Structure | Applies in some cases | requires=unstructured; requires=semi-structured |
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=document |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | A fixed set of fields, defined before extraction, that are stated explicitly in the text. |
|---|---|
| Additional sources needed | reference structure |
| Not for (rules) | none |
| Not for (text) | Fields are not explicit in the text and the model must infer them without those values being flagged as inferred. |
Choosing and ordering
| Kind of technique | Preparation technique, runs in step 5.2 |
|---|---|
| Phase tag | verify and prepare |
| Other phase tags | analyse |
| Kind of finding | gap; pattern |
| Question answered | how much; what |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | proceed with limit stated |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: repeatable with fixed settings.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | spot check | optional | no |
| decision-informing | spot check | optional | no |
| decision-informing | human review sample | needed; left out below high stakes | no |
| decision-informing | source-span citation | none | no |
| decision-informing | prompt variation | none | no |
| high-stakes | spot check | optional | no |
| high-stakes | human review sample | needed | no |
| high-stakes | source-span citation | none | no |
| high-stakes | prompt variation | none | no |
| high-stakes | gold standard agreement | conditional | no |
| high-stakes | provenance log | none | no |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | model plus code |
|---|---|
| Typical model failure | Invents a value for a field that the document does not state instead of returning not stated. |
| Error sources | input data; data transformation; language model |
| Certainty limits | Certainty drops when accuracy was not measured for the task (indirectness), when fields are inferred (risk of bias), or when not stated rates are high (imprecision). |
Related techniques
- pairs with CK-04 Gold-standard validation sample (ground truth set; human-coded validation set): a gold-standard sample measures field accuracy for each task
- pairs with CK-17 Source-span and quotation check by code (quote-and-verify; extractive grounding; citation verification): a source-span check by code confirms that each value appears in the source
Evidence and tag basis
Tested. GPT-4 performance across 27 annotation tasks and 11 datasets depended heavily on dataset and task (2023, abstract). (Pangakis et al., arXiv 2306.00176; Halterman and Keith, arXiv 2407.10747)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.