Triple
T10490449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berta languages |
E247403
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Berta language group |
C28123
|
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: Berta language group Context triple: [Berta languages, instanceOf, Berta language group]
-
A.
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.
-
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.
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.
-
D.
Cordilleran language
A Cordilleran language is a member of a proposed subgroup of the Austronesian language family spoken in the Cordillera mountain region of northern Luzon in the Philippines, characterized by shared phonological, lexical, and grammatical features distinct from neighboring language groups.
-
E.
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.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:23 p.m.