Triple
T17005094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roth IRA |
E412548
|
entity |
| Predicate | beneficiaryDesignationAllowed |
P37866
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Roth IRA, beneficiaryDesignationAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficiaryDesignationAllowed Context triple: [Roth IRA, beneficiaryDesignationAllowed, yes]
-
A.
beneficiaryChangeAllowed
chosen
Indicates that changing or updating the designated beneficiary is permitted under the relevant rules or agreement.
-
B.
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.
-
C.
eligibleBeneficiaries
Indicates that certain parties meet the required conditions to receive benefits or entitlements under a given rule or program.
-
D.
beneficiaryMayHave
Indicates that a beneficiary is allowed or permitted to possess, receive, or be associated with something.
-
E.
beneficiarySelectionMethod
Indicates the way in which a beneficiary is chosen or determined in relation to an action, agreement, or resource.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d382400c819092ec0ca0de815888 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.