Triple

T16033570
Position Surface form Disambiguated ID Type / Status
Subject South Omotic E388909 entity
Predicate instanceOf P0 FINISHED
Object Omotic language branch 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 branch
Context triple: [South Omotic, instanceOf, Omotic language branch]
  • 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. Afroasiatic language branch
    The Afroasiatic language branch is a major language family originating in the Middle East and North Africa, encompassing diverse languages such as Arabic, Hebrew, Amharic, and Hausa that share common historical and structural features.
  • D. 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.
  • E. 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.
  • 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.