Triple
T2371699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon 529 college savings programs |
E46103
|
entity |
| Predicate | taxAdvantaged |
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: [Oregon 529 college savings programs, taxAdvantaged, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taxAdvantaged Context triple: [Oregon 529 college savings programs, taxAdvantaged, true]
-
A.
taxType
Indicates the specific category or classification of tax that applies to an entity, transaction, or amount.
-
B.
benefitTaxStatus
chosen
Indicates that an entity’s tax-related status or classification provides a financial or regulatory benefit in the context of the relationship.
-
C.
taxAuthority
Indicates that an entity serves as the official body responsible for assessing, collecting, and enforcing taxes over another entity or within a jurisdiction.
-
D.
taxpayerBenefitForm
Indicates that there is a specific form documenting or enabling a benefit granted to a taxpayer.
-
E.
notableAdvantage
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc771302481908540e31abb5aeeba |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.