Triple
T22930768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Deever |
E569431
|
entity |
| Predicate | relationshipToGeorgeDeever |
P150297
|
FINISHED |
| Object | father |
—
|
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 | Statement: [Steve Deever, relationshipToGeorgeDeever, father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToGeorgeDeever Context triple: [Steve Deever, relationshipToGeorgeDeever, father]
-
A.
relationshipToAnnDeever
Indicates the specific interpersonal or familial relationship that an entity has to Ann Deever.
-
B.
relationshipToGeorgeWilson
Indicates the specific nature of the relationship or connection that an entity has to George Wilson.
-
C.
relationshipToGeorgePage
Indicates the specific familial, social, or professional relationship that an entity has to George Page.
-
D.
relationshipToGeorgeAndMartha
Indicates the specific familial, social, or other relational connection that an entity has to the pair George and Martha considered together.
-
E.
relationshipToJimDear
Indicates a familial, romantic, or otherwise significant personal relationship that an entity has with the person referred to as Jim Dear.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18131956c8190b8c850fc1d57a119 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:44 p.m.