Triple
T31282411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1040-A |
E797705
|
entity |
| Predicate | allowedDeductions |
P171173
|
FINISHED |
| Object | standard deduction |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: standard deduction | Statement: [Form 1040-A, allowedDeductions, standard deduction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedDeductions Context triple: [Form 1040-A, allowedDeductions, standard deduction]
-
A.
taxDeductible
Indicates that an expense, contribution, or item is eligible to be subtracted from taxable income under applicable tax rules.
-
B.
deductsFrom
Indicates that a specified amount, value, or resource is subtracted from another entity, reducing the latter accordingly.
-
C.
deductionType
chosen
Indicates the specific kind or category of deduction that applies within a given context or system.
-
D.
allowancesType
Indicates the specific category or kind of allowances associated with an entity or transaction.
-
E.
taxationApprovedFor
Indicates that an authority has formally approved the imposition or application of a specific tax on a particular entity or activity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 9:13 p.m.