Triple

T35976817
Position Surface form Disambiguated ID Type / Status
Subject Nebraska Ho-Chunk dialect E1040442 entity
Predicate instanceOf P0 FINISHED
Object regional variety of the Ho-Chunk language C62650 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: regional variety of the Ho-Chunk language
Context triple: [Nebraska Ho-Chunk dialect, instanceOf, regional variety of the Ho-Chunk language]
  • A. variety of the Ho-Chunk language chosen
    A variety of the Ho-Chunk language is a distinct regional or social form of Ho-Chunk characterized by systematic differences in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible with other forms.
  • B. Kickapoo language variety
    A Kickapoo language variety is a specific dialect or form of the Kickapoo language, distinguished by its unique phonological, lexical, and grammatical features used by particular Kickapoo-speaking communities.
  • C. Pawnee language variety
    A Pawnee language variety is a specific form or dialect of the Pawnee language distinguished by unique phonological, lexical, or grammatical features associated with particular speaker communities or regions.
  • D. regional variety of the Choctaw language
    A regional variety of the Choctaw language is a geographically distinct form of Choctaw characterized by unique phonological, lexical, or grammatical features shared by speakers in a particular area.
  • E. 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.
  • 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_69f76e27758c81909b711cf38a130aaf completed May 3, 2026, 3:47 p.m.
Created at: May 3, 2026, 4:07 p.m.