Triple
T23420296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRIF |
E560631
|
entity |
| Predicate | isTaxAdvantaged |
P24100
|
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: [RRIF, isTaxAdvantaged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTaxAdvantaged Context triple: [RRIF, isTaxAdvantaged, true]
-
A.
benefitTaxStatus
chosen
Indicates that an entity’s tax-related status or classification provides a financial or regulatory benefit in the context of the relationship.
-
B.
taxationApprovedFor
Indicates that an authority has formally approved the imposition or application of a specific tax on a particular entity or activity.
-
C.
isTaxable
Indicates that the subject is legally subject to taxation under the applicable tax rules or regulations.
-
D.
taxDeductible
Indicates that an expense, contribution, or item is eligible to be subtracted from taxable income under applicable tax rules.
-
E.
isDiscretionary
Indicates that the action or decision is optional and left to personal or organizational judgment rather than being mandatory or automatic.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54605dc81909aad9834ef6ff8a1 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:44 p.m.