Triple
T36631439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mbay language |
E904328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bongo–Bagirmi language |
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: Bongo–Bagirmi language Context triple: [Mbay language, instanceOf, Bongo–Bagirmi language]
-
A.
Kadugli–Krongo language
The Kadugli–Krongo language is a small group of closely related Kadu (Kadugli) languages spoken primarily in the Nuba Mountains of Sudan, characterized by complex tone systems and rich noun morphology.
-
B.
Bamileke language
Bamileke language refers to a group of closely related Grassfields Bantu languages spoken primarily by the Bamileke people in western Cameroon.
-
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.
Songhay language
Songhay language is a group of closely related Nilo-Saharan languages spoken primarily along the Niger River in Mali, Niger, and neighboring West African countries.
-
E.
Grassfields language
A Grassfields language is a member of a subgroup of Southern Bantoid languages spoken primarily in the Grassfields region of western Cameroon, characterized by complex noun class systems and tonal distinctions.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.