Triple
T33210029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy Phelan |
E850127
|
entity |
| Predicate | beneficiaryOfWill |
P45732
|
FINISHED |
| Object | Rachel Lane |
—
|
NE NERFINISHED |
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: Rachel Lane | Statement: [Troy Phelan, beneficiaryOfWill, Rachel Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficiaryOfWill Context triple: [Troy Phelan, beneficiaryOfWill, Rachel Lane]
-
A.
willBequest
Indicates a relationship where a person specifies in a will that certain assets or rights are to be given to another party after their death.
-
B.
resultOfBequest
Indicates that something exists or occurs as the outcome of a bequest made in a will or similar testamentary act.
-
C.
bequestEstablished
Indicates that a bequest has been formally created or put into effect, establishing a legally recognized transfer of assets upon someone’s death.
-
D.
bequeathedBy
chosen
Indicates that something has been left or passed on to an entity through the will or inheritance of another entity.
-
E.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:30 a.m.