Triple
T13236651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 97-34 |
E315162
|
entity |
| Predicate | introducedIndexationOfTaxBrackets |
P14569
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Public Law 97-34, introducedIndexationOfTaxBrackets, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedIndexationOfTaxBrackets Context triple: [Public Law 97-34, introducedIndexationOfTaxBrackets, true]
-
A.
changesIndividualIncomeTaxBrackets
Indicates that an action or policy alters the structure or thresholds of individual income tax brackets.
-
B.
introducedTaxType
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
-
C.
benefitIndexation
chosen
Indicates that a benefit amount is adjusted over time according to an index (such as inflation or wage growth).
-
D.
introducedInTaxYear
Indicates that something (such as a rule, benefit, or provision) first became applicable or was brought into effect in a specified tax year.
-
E.
taxationMethod
Indicates the specific way or system by which taxes are calculated, collected, or applied in a given context.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d56da008190af55da3a9e7ffd4d |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.