Triple
T31133055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynn Belvedere |
E793562
|
entity |
| Predicate | guidesFamily |
P171180
|
FINISHED |
| Object | Owens family |
—
|
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: Owens family | Statement: [Lynn Belvedere, guidesFamily, Owens family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidesFamily Context triple: [Lynn Belvedere, guidesFamily, Owens family]
-
A.
guidanceKitFamily
Indicates a relationship where one entity belongs to, or is categorized within, a particular family or group of guidance kits.
-
B.
familyAttraction
Indicates a relationship where one entity feels a romantic or sexual attraction toward a member of their own family.
-
C.
familyClass
Indicates that an entity belongs to, or is categorized within, a particular family grouping or class in a familial or taxonomic hierarchy.
-
D.
fareFamily
Indicates a relationship that classifies a fare or ticket into a specific fare family or category within a pricing structure.
-
E.
leadsFamilyOf
Indicates that one entity holds primary leadership or head-of-household authority over a particular family unit.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c6e0b888190a417ae712c42db0d |
completed | May 3, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f69c2127088190ae92c72461576d3b |
completed | May 3, 2026, 12:51 a.m. |
Created at: April 29, 2026, 9:05 p.m.