Triple
T29651586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revenue Act of 1962 |
E750146
|
entity |
| Predicate | hasTaxInstrument |
P172159
|
FINISHED |
| Object | tax credit |
—
|
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: tax credit | Statement: [Revenue Act of 1962, hasTaxInstrument, tax credit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaxInstrument Context triple: [Revenue Act of 1962, hasTaxInstrument, tax credit]
-
A.
hasTaxPolicyResponsibility
Indicates that an entity holds authority or duty for creating, managing, or overseeing tax-related policies for another entity or jurisdiction.
-
B.
hasOwnTaxSystem
Indicates that an entity maintains and administers its own distinct system of taxation, separate from other jurisdictions or authorities.
-
C.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
D.
taxOn
Indicates that one entity imposes or applies a tax on another entity or item.
-
E.
customsInstrument
Indicates that one entity serves as a tool, method, or means used by customs authorities to perform or facilitate a customs-related action involving 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 6:52 p.m.