Triple
T35624388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 97-34 |
E1029409
|
entity |
| Predicate | effectOnBusinessTaxation |
P39307
|
FINISHED |
| Object | introduced accelerated cost recovery system |
—
|
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: introduced accelerated cost recovery system | Statement: [97-34, effectOnBusinessTaxation, introduced accelerated cost recovery system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnBusinessTaxation Context triple: [97-34, effectOnBusinessTaxation, introduced accelerated cost recovery system]
-
A.
effectOnTaxes
chosen
Indicates how one entity or action changes, influences, or determines the amount, structure, or treatment of taxes for another entity or situation.
-
B.
impactOnBusiness
Indicates the effect or influence that one factor, event, or action has on a business’s performance, operations, or outcomes.
-
C.
viewOnTaxation
Indicates a person's stance or opinion regarding taxation policies or tax levels.
-
D.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
E.
positionOnTaxation
Indicates a stance or viewpoint an entity holds regarding tax policies, levels, or structures.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.