Triple
T16903028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revenue Act of 1971 |
E424485
|
entity |
| Predicate | typeOfTaxChange |
P125139
|
FINISHED |
| Object | rate adjustments |
—
|
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: rate adjustments | Statement: [Revenue Act of 1971, typeOfTaxChange, rate adjustments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTaxChange Context triple: [Revenue Act of 1971, typeOfTaxChange, rate adjustments]
-
A.
corporateTaxRateChangeType
Indicates the type or nature of a change applied to a corporate tax rate (e.g., increase, decrease, introduction, or removal).
-
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.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
D.
changesCorporateTaxSystem
Indicates that an entity alters, reforms, or replaces an existing corporate tax system or its rules.
-
E.
typeOfTaxCredit
Indicates that one entity is a specific kind or category of tax credit in relation to another entity.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dd2bf08190b1dc099e8a23cd04 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:30 a.m.