Triple
T20820221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Bledsoe |
E512554
|
entity |
| Predicate | returnsHomeFor |
P45021
|
FINISHED |
| Object | father’s funeral |
—
|
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: father’s funeral | Statement: [Frank Bledsoe, returnsHomeFor, father’s funeral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsHomeFor Context triple: [Frank Bledsoe, returnsHomeFor, father’s funeral]
-
A.
returnsTo
chosen
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
-
B.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
D.
supportsReturnToHome
Indicates that an entity provides or enables a “return to home” function, allowing something to automatically go back to its predefined starting or home location.
-
E.
previousHome
Indicates that one entity served as a former or prior residence or home of another entity.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f6a65481909a0df78616e185e4 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.