Triple
T23420313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRIF |
E560631
|
entity |
| Predicate | canNameBeneficiary |
P152205
|
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, canNameBeneficiary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canNameBeneficiary Context triple: [RRIF, canNameBeneficiary, true]
-
A.
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.
-
B.
beneficiaryChangeAllowed
Indicates that changing or updating the designated beneficiary is permitted under the relevant rules or agreement.
-
C.
hasBeneficiaryTitle
Indicates that a beneficiary holds or is assigned a specific formal title or designation in the context of a relationship or arrangement.
-
D.
beneficiaryMayHave
Indicates that a beneficiary is allowed or permitted to possess, receive, or be associated with something.
-
E.
beneficiaryType
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:44 p.m.