Triple
T16115816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 115-97 |
E390998
|
entity |
| Predicate | corporateTaxRateChangeType |
P121534
|
FINISHED |
| Object | permanent |
—
|
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: permanent | Statement: [Public Law 115-97, corporateTaxRateChangeType, permanent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateTaxRateChangeType Context triple: [Public Law 115-97, corporateTaxRateChangeType, permanent]
-
A.
changesCorporateTaxSystem
Indicates that an entity alters, reforms, or replaces an existing corporate tax system or its rules.
-
B.
corporateTaxRate
Indicates the percentage of a corporation’s taxable income that is owed as tax under the applicable tax regime.
-
C.
topCorporateRateAfterReform
Indicates the highest corporate tax rate that applies following the implementation of a specified tax reform.
-
D.
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.
-
E.
topCorporateRateBeforeReform
Indicates the highest corporate tax rate that was in effect prior to a specified tax reform or policy change.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016a9dd48190bca3f58778ed865f |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.