Triple
T31966175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith family of St. Louis |
E816181
|
entity |
| Predicate | familyRoleOf |
P38221
|
FINISHED |
| Object | Alonzo Smith; 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: Alonzo Smith; father | Statement: [Smith family of St. Louis, familyRoleOf, Alonzo Smith; father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyRoleOf Context triple: [Smith family of St. Louis, familyRoleOf, Alonzo Smith; father]
-
A.
familyOrganizerRole
Indicates the specific role or capacity an individual holds as the organizer or manager within a family group or household.
-
B.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
E.
familyContext
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 12:09 a.m.