Triple
T33830254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maban branch of Nilo-Saharan |
E867077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maban languages |
C58423
|
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: Maban languages Context triple: [Maban branch of Nilo-Saharan, instanceOf, Maban languages]
-
A.
Bantoid languages
Bantoid languages are a branch of the Benue–Congo family within the Niger–Congo language phylum, comprising Bantu and closely related non-Bantu languages spoken primarily in Central and West Africa.
-
B.
Banda languages
Banda languages are a group of closely related Ubangian languages spoken primarily in the Central African Republic and neighboring regions, characterized by shared phonological and grammatical features.
-
C.
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.
-
D.
Munda language
The Munda language is a member of the Austroasiatic language family spoken primarily by indigenous Munda communities in eastern and central India, characterized by agglutinative morphology and distinct phonological features.
-
E.
Chamic language
A Chamic language is any member of a subgroup of the Austronesian language family spoken primarily in parts of Vietnam, Cambodia, Thailand, and Hainan, historically associated with the Cham people and related ethnic groups.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.