Triple
T25659189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobo–Bozo languages |
E643329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mande language subgroup |
C7393
|
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: Mande language subgroup Context triple: [Bobo–Bozo languages, instanceOf, Mande language subgroup]
-
A.
Mande language
chosen
A Mande language is a member of a branch of the Niger-Congo language family spoken primarily in West Africa, characterized by tonal systems, isolating morphology, and a shared historical origin among its diverse regional varieties.
-
B.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
C.
Volta–Niger language
A Volta–Niger language is a member of a proposed branch of the Niger–Congo language family spoken primarily in southern Nigeria and neighboring regions, characterized by significant lexical and grammatical diversity among its constituent languages.
-
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.
subgroup of Niger–Congo languages
A subgroup of Niger–Congo languages is a set of closely related languages within the Niger–Congo family that share a common ancestral origin and distinctive structural and lexical 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 6:49 p.m.