Triple
T37049077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gikuyu–Embu–Meru peoples |
E917000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous peoples of Africa |
C7545
|
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: indigenous peoples of Africa Context triple: [Gikuyu–Embu–Meru peoples, instanceOf, indigenous peoples of Africa]
-
A.
African people
African people are the diverse populations originating from the African continent, encompassing a wide range of ethnicities, cultures, languages, histories, and lived experiences.
-
B.
West African people
West African people are diverse ethnic and cultural groups indigenous to the western region of Africa, sharing interconnected histories, languages, traditions, and social structures shaped by centuries of migration, trade, and adaptation.
-
C.
Bantu people
chosen
The Bantu people are a large, diverse group of African ethnic communities linked by related Bantu languages and shared historical origins in central and western Africa, whose migrations significantly shaped the continent’s cultural, linguistic, and demographic landscape.
-
D.
African culture
African culture encompasses the diverse traditions, languages, arts, beliefs, and social practices of the many ethnic groups across the African continent, shaped by rich histories, environments, and intercultural exchanges.
-
E.
Nilotic people
Nilotic people are a diverse group of ethnolinguistic communities indigenous to the Nile Valley and surrounding regions of East and Central Africa, sharing related Nilotic languages and many cultural traditions.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.