Triple
T31183661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form 1040-EZ |
E794970
|
entity |
| Predicate | notAvailableForTaxYear |
P171227
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Form 1040-EZ, notAvailableForTaxYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAvailableForTaxYear Context triple: [Form 1040-EZ, notAvailableForTaxYear, 2018]
-
A.
appliesToTaxYear
Indicates the specific tax year or fiscal period to which a tax-related rule, record, or obligation is applicable.
-
B.
introducedInTaxYear
Indicates that something (such as a rule, benefit, or provision) first became applicable or was brought into effect in a specified tax year.
-
C.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
D.
notHeldFollowingYear
Indicates that an event or activity that occurred in one year did not take place in the immediately following year.
-
E.
nonEligibility
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
- F. None of above. chosen
Provenance (4 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6f01e881908fa84f5d429d37ae |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:08 p.m.