Triple
T24483294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts College Savings Programs |
E617435
|
entity |
| Predicate | canChangeBeneficiary |
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: [Massachusetts College Savings Programs, canChangeBeneficiary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canChangeBeneficiary Context triple: [Massachusetts College Savings Programs, canChangeBeneficiary, 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.
canNameBeneficiary
Indicates that an entity has the authority or ability to designate another entity as a beneficiary.
-
E.
beneficiaryActionMethod
Indicates that an action benefiting a recipient is carried out using a particular method or means.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:21 a.m.