Triple

T14576106
Position Surface form Disambiguated ID Type / Status
Subject River Yuman E342054 entity
Predicate instanceOf P0 FINISHED
Object Yuman language branch C34966 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: Yuman language branch
Context triple: [River Yuman, instanceOf, Yuman language branch]
  • A. Munda languages subgroup
    The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
  • B. Yana language variety
    Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
  • C. Gumuz language variety
    A Gumuz language variety is a specific form or dialect of the Gumuz language, distinguished by its unique phonological, lexical, or grammatical features within the broader Gumuz linguistic continuum.
  • D. 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.
  • E. branch of Austroasiatic languages
    A branch of Austroasiatic languages is a subgroup within the Austroasiatic language family whose member languages share a common historical origin and distinctive linguistic features.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
Created at: April 10, 2026, 1:24 a.m.