Triple
T8033440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooper Bay–Chevak dialect |
E187042
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yup'ik language variety |
C23431
|
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: Yup'ik language variety Context triple: [Hooper Bay–Chevak dialect, instanceOf, Yup'ik language variety]
-
A.
Inuit language
Inuit language is a group of closely related Indigenous languages spoken across the Arctic regions of Alaska, Canada, and Greenland, characterized by polysynthetic word formation and rich expression of environmental and cultural concepts.
-
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.
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.
Tsimshianic language
A Tsimshianic language is any member of a small family of Indigenous languages of the Pacific Northwest Coast of North America, traditionally spoken by the Tsimshian peoples of British Columbia and Alaska.
-
E.
Yavapai language variety
A Yavapai language variety is a specific form or dialect of the Yavapai language, distinguished by unique phonological, lexical, or grammatical features used by a particular Yavapai-speaking community.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:22 p.m.