Triple
T34599077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinasha |
E888404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | North Omotic language |
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: North Omotic language Context triple: [Shinasha, instanceOf, North Omotic language]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
South Ethiopic Semitic language
A South Ethiopic Semitic language is a member of the Semitic branch of the Afroasiatic family spoken in southern Ethiopia, characterized by shared phonological, morphological, and syntactic features distinct to this regional subgroup.
-
E.
Cushitic language subgroup
A Cushitic language subgroup is a branch within the Cushitic family of Afroasiatic languages, comprising closely related languages that share common historical origins and structural features.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.