Triple

T35901855
Position Surface form Disambiguated ID Type / Status
Subject Jova E1038371 entity
Predicate instanceOf P0 FINISHED
Object variety of the Opata language C62496 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: variety of the Opata language
Context triple: [Jova, instanceOf, variety of the Opata language]
  • A. variety of the Katu language
    A variety of the Katu language is a distinct regional or social form of Katu characterized by systematic differences in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible with other Katu forms.
  • B. variety of the Kati language
    A variety of the Kati language is a distinct regional or social form of Kati characterized by its own systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Kati forms.
  • C. Otomi language variety
    An Otomi language variety is a specific regional or social form of the Otomi language, distinguished by its own phonological, lexical, and grammatical features within the broader Otomi linguistic continuum.
  • D. variety of the Terena language
    A variety of the Terena language is a distinct regional or social form of Terena characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
  • E. variety of the Uma language
    A variety of the Uma language is a distinct regional or social form of Uma characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
  • 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_69f76e2190f88190beb2eed798a4ef01 completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:07 p.m.