Triple
T16033597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamo-Gofa-Dawro |
E388910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Omotic language group |
C17901
|
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: Omotic language group Context triple: [Gamo-Gofa-Dawro, instanceOf, Omotic language group]
-
A.
Omotic language
chosen
An Omotic language is any member of a group of Afroasiatic languages spoken primarily in southwestern Ethiopia, characterized by significant internal diversity and debated classification within the Afroasiatic family.
-
B.
Nilo-Saharan language
A Nilo-Saharan language is a member of a proposed but controversial language family spoken primarily along the Nile and across parts of central and eastern Africa, characterized by significant internal diversity and debated genetic relationships.
-
C.
Cushitic language
A Cushitic language is a member of a branch of the Afroasiatic language family spoken primarily in the Horn of Africa and parts of East Africa, characterized by shared grammatical and phonological features distinct from other Afroasiatic branches.
-
D.
Chadic language
A Chadic language is any member of a branch of the Afroasiatic language family spoken primarily in parts of Nigeria, Niger, Chad, Cameroon, and neighboring regions, characterized by diverse phonological systems and complex verb morphology.
-
E.
Hurro-Urartian language
A Hurro-Urartian language is a member of an extinct family of ancient Near Eastern languages, primarily known from cuneiform inscriptions of the Hurrians and Urartians in the second and first millennia BCE.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.