Triple
T21915657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Underwood–Simmons Act |
E541176
|
entity |
| Predicate | introducedFederalIncomeTax |
P66045
|
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: [Underwood–Simmons Act, introducedFederalIncomeTax, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFederalIncomeTax Context triple: [Underwood–Simmons Act, introducedFederalIncomeTax, true]
-
A.
introducedTaxType
chosen
Indicates that an entity (such as a government or authority) has brought a particular type of tax into existence or put it into effect.
-
B.
taxationPowerOfCongress
Indicates Congress’s authority to impose, collect, and regulate taxes and related levies.
-
C.
federalPartCameIntoForce
Indicates that a specific part of a federal law or regulation has officially taken legal effect from a certain point in time.
-
D.
taxBurden
Indicates the extent to which an entity is obligated to pay taxes, typically reflecting the level or share of tax liability it bears.
-
E.
introducedByLaw
Indicates that something (such as a rule, measure, or change) came into effect or was established as a result of a specific law being enacted.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123378140819090a30453c1db7f38 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:42 p.m.