Triple
T24064259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikar language |
E596043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Bantoid language |
C20849
|
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: Northern Bantoid language Context triple: [Tikar language, instanceOf, Northern Bantoid language]
-
A.
Bantoid languages
chosen
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.
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.
-
C.
Oto-Manguean language
An Oto-Manguean language is a member of a large, diverse family of indigenous Mesoamerican languages, primarily spoken in Mexico, characterized by complex tonal systems and significant grammatical and phonological variation.
-
D.
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.
-
E.
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.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:39 p.m.