Triple
T6110078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mellon tax cuts of the 1920s |
E136213
|
entity |
| Predicate | affectedTaxType |
P39307
|
FINISHED |
| Object | federal individual income tax |
—
|
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: federal individual income tax | Statement: [Mellon tax cuts of the 1920s, affectedTaxType, federal individual income tax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedTaxType Context triple: [Mellon tax cuts of the 1920s, affectedTaxType, federal individual income tax]
-
A.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
effectOnTaxes
chosen
Indicates how one entity or action changes, influences, or determines the amount, structure, or treatment of taxes for another entity or situation.
-
C.
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.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b84ed088190a12cdb844d743326 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.