Triple

T5316181
Position Surface form Disambiguated ID Type / Status
Subject Wolaytta E119153 entity
Predicate instanceOf P0 FINISHED
Object 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: Omotic language
Context triple: [Wolaytta, instanceOf, Omotic language]
  • A. 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.
  • B. 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.
  • 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. Uralic language
    A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
  • E. 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.
  • 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_69bd446b57bc8190a513d2e6c40314f3 completed March 20, 2026, 12:58 p.m.
Created at: March 20, 2026, 1:54 p.m.