Triple
T24583628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbam–Nkam languages |
E608320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grassfields language subgroup |
C48477
|
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: Grassfields language subgroup Context triple: [Mbam–Nkam languages, instanceOf, Grassfields language subgroup]
-
A.
Ubangian language
A Ubangian language is a member of a proposed group of Central African languages, primarily spoken in the Central African Republic and neighboring countries, that share common phonological and grammatical features and are often considered a branch of the Niger-Congo family.
-
B.
Nilotic language
A Nilotic language is a member of a group of related languages spoken primarily along the Nile Valley and surrounding regions of East Africa, characterized by shared grammatical and phonological features.
-
C.
Nilotic language
A Nilotic language is a member of a group of related languages spoken primarily along the Nile Valley and surrounding regions of East Africa, characterized by shared grammatical structures and vocabulary.
-
D.
Central Khoisan language
A Central Khoisan language is a member of the Khoisan language family spoken primarily in central southern Africa, characterized by extensive use of click consonants and complex phonological systems.
-
E.
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.
- F. None of above. chosen
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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:29 a.m.