Triple

T36261232
Position Surface form Disambiguated ID Type / Status
Subject Illinois 529 college savings plans E892091 entity
Predicate beneficiaryCanBeChanged P37866 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: [Illinois 529 college savings plans, beneficiaryCanBeChanged, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: beneficiaryCanBeChanged
Context triple: [Illinois 529 college savings plans, beneficiaryCanBeChanged, true]
  • A. beneficiaryChangeAllowed chosen
    Indicates that changing or updating the designated beneficiary is permitted under the relevant rules or agreement.
  • B. beneficiaryChangeRule
    Indicates a rule or condition governing how, when, or under what circumstances a beneficiary of something may be changed.
  • C. canHaveBeneficiary
    Indicates that an entity is capable of having another party designated as its beneficiary, who may receive benefits, rights, or proceeds associated with it.
  • D. otherBeneficiary
    Indicates that an entity receives a benefit or advantage from something, in addition to the primary or explicitly named beneficiary.
  • E. beneficiaryMayHave
    Indicates that a beneficiary is allowed or permitted to possess, receive, or be associated with something.
  • 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_69f76e4699188190af045b11a840ce31 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7be9d07ac8190adf796cbef60daf6 completed May 3, 2026, 9:31 p.m.
PD Predicate disambiguation batch_69f7bcccd7988190aa5c931ff347d33c completed May 3, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:09 p.m.