Triple
T9146226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pretorius family |
E219461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boer family |
C18383
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Boer family Context triple: [Pretorius family, instanceOf, Boer family]
-
A.
South African family
chosen
A South African family is a social unit connected by kinship, marriage, or adoption within the South African context, typically characterized by diverse cultural traditions, multilingualism, and intergenerational support structures.
-
B.
Swiss family
A Swiss family is a household unit originating from or residing in Switzerland, typically characterized by multilingualism, strong ties to Swiss cultural traditions, and integration into the country’s social and civic life.
-
C.
Georgian family
A Georgian family is a close-knit household typically spanning multiple generations, characterized by strong traditions, deep respect for elders, and warm hospitality rooted in Georgian culture.
-
D.
Ukrainian family
A Ukrainian family is a close-knit household unit typically characterized by strong intergenerational bonds, deep cultural traditions, and mutual support rooted in Ukrainian heritage and values.
-
E.
noble family
A noble family is a socially and often legally recognized kinship group that holds hereditary titles, privileges, and status within a hierarchical society, typically associated with landownership, political influence, and longstanding lineage.
- F. None of above.
Provenance (1 batch)
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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:19 p.m.