Triple
T26751509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sere–Mba languages |
E674549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ubangian language subgroup |
C22855
|
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: Ubangian language subgroup Context triple: [Sere–Mba languages, instanceOf, Ubangian language subgroup]
-
A.
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.
-
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.
Ubangian language
chosen
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.
-
D.
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.
-
E.
Igbo subgroup
An Igbo subgroup is a distinct cultural, linguistic, and often geographically based division within the broader Igbo ethnic group, characterized by shared traditions, dialects, and social identities.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:53 a.m.