Triple

T31722087
Position Surface form Disambiguated ID Type / Status
Subject Chevak Cup’ik dialect E809610 entity
Predicate instanceOf P0 FINISHED
Object Central Alaskan Yup’ik variety C23430 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: Central Alaskan Yup’ik variety
Context triple: [Chevak Cup’ik dialect, instanceOf, Central Alaskan Yup’ik variety]
  • A. Yup'ik language variety
    A Yup'ik language variety is a specific regional or social form of the Yup'ik language distinguished by its unique phonological, lexical, and grammatical features within the broader Yup'ik linguistic continuum.
  • B. variety of Central Alaskan Yup'ik chosen
    A variety of Central Alaskan Yup'ik is a specific regional or social form of the Central Alaskan Yup'ik language characterized by distinct phonological, lexical, and grammatical features within the broader Yup'ik-speaking community.
  • C. Southern Wakashan language
    A Southern Wakashan language is a member of the southern branch of the Wakashan language family, traditionally spoken by Indigenous peoples of the Pacific Northwest Coast, particularly on Vancouver Island and adjacent mainland areas.
  • D. Aleut language
    Aleut language is an indigenous Eskimo-Aleut language spoken by the Aleut people of the Aleutian Islands and nearby regions, known for its polysynthetic structure and complex verb morphology.
  • E. Chinookan language variety
    A Chinookan language variety is a specific form or dialect of the Chinookan language family traditionally spoken by Indigenous Chinookan peoples of the Pacific Northwest, characterized by its own phonological, grammatical, and lexical features.
  • 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_69f348e009c8819095d77df52c645b9c completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:19 p.m.