Triple
T3822142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tax Cuts and Jobs Act of 2017 |
E88596
|
entity |
| Predicate | changesStandardDeduction |
P24476
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tax Cuts and Jobs Act of 2017, changesStandardDeduction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changesStandardDeduction Context triple: [Tax Cuts and Jobs Act of 2017, changesStandardDeduction, yes]
-
A.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
-
B.
typicalRuleModification
chosen
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
C.
benefitTaxStatus
Indicates that an entity’s tax-related status or classification provides a financial or regulatory benefit in the context of the relationship.
-
D.
extendsStandard
Indicates that one entity builds upon, enhances, or adds to an existing standard defined by another entity.
-
E.
isAmendmentTo
Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.