Triple
T28889125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caledon Hockley |
E732645
|
entity |
| Predicate | relationshipToRoseFamily |
P202556
|
FINISHED |
| Object | approved by Ruth DeWitt Bukater |
—
|
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: approved by Ruth DeWitt Bukater | Statement: [Caledon Hockley, relationshipToRoseFamily, approved by Ruth DeWitt Bukater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRoseFamily Context triple: [Caledon Hockley, relationshipToRoseFamily, approved by Ruth DeWitt Bukater]
-
A.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
B.
subjectFamilyRelation
Indicates that there is a familial relationship of some kind between the subject entity and another entity.
-
C.
relationshipToMary
Indicates that one entity stands in a specified personal or social relationship to Mary.
-
D.
relationshipToRosalind
Indicates the specific type of personal or familial connection an entity has to Rosalind.
-
E.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_6a0091ac9ff08190b635eac6aa3f6128 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 28, 2026, 7:53 a.m.