Triple
T27804102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guthrie Zone H |
E702327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bantu language classification zone |
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: Bantu language classification zone Context triple: [Guthrie Zone H, instanceOf, Bantu language classification zone]
-
A.
Bantu language
A Bantu language is a member of a large branch of the Niger-Congo language family, spoken primarily in central, eastern, and southern Africa, characterized by noun class systems and agglutinative morphology.
-
B.
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.
-
C.
linguistic classification zone
A linguistic classification zone is a conceptual area or domain within which languages, dialects, or speech varieties are grouped and analyzed based on shared structural, historical, or sociolinguistic features.
-
D.
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.
-
E.
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.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:37 p.m.