Triple

T33342135
Position Surface form Disambiguated ID Type / Status
Subject Bantu Zone B E853698 entity
Predicate instanceOf P0 FINISHED
Object Guthrie Bantu classification subgroup C32209 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: Guthrie Bantu classification subgroup
Context triple: [Bantu Zone B, instanceOf, Guthrie Bantu classification subgroup]
  • A. Guthrie Bantu zone chosen
    The Guthrie Bantu zone is a classification grouping within Malcolm Guthrie’s geographic-phonological system that organizes Bantu languages into labeled regions (zones) based on their distribution and shared linguistic features.
  • B. Bantu people
    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.
  • C. Grassfields language subgroup
    The Grassfields language subgroup is a branch of the Southern Bantoid languages spoken primarily in the Grassfields region of western Cameroon, characterized by significant internal diversity and complex noun class systems.
  • D. Bantu state
    A Bantu state is a political entity historically or contemporarily governed by Bantu-speaking peoples, typically characterized by centralized authority, kinship-based social organization, and economies rooted in agriculture, herding, and regional trade.
  • E. Gond subgroup
    A Gond subgroup is a distinct clan or community division within the larger Gond ethnic group, characterized by shared ancestry, cultural practices, and social organization.
  • 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_69f3496a1a588190bad9cbe9221144e0 completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:34 a.m.