Triple
T1533738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooper Bay–Chevak |
E32503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Alaskan Yup’ik dialect |
C2570
|
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 dialect Context triple: [Hooper Bay–Chevak, instanceOf, Central Alaskan Yup’ik dialect]
-
A.
Inuit language
chosen
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.
Algonquian language
An Algonquian language is any member of a family of Indigenous languages of North America, historically spoken from the Atlantic coast to the Great Plains and characterized by complex morphology and polysynthetic structure.
-
C.
Athabaskan-speaking people
Athabaskan-speaking people are Indigenous groups of North America whose diverse cultures and communities are linked by related Athabaskan (Dene) languages spread across Alaska, northwestern Canada, and the American Southwest.
-
D.
Uto-Aztecan language
A Uto-Aztecan language is a member of a Native American language family spoken from the western United States through northern and central Mexico, sharing common ancestral linguistic features despite diverse cultures and regions.
-
E.
borough of Alaska
A borough of Alaska is a regional administrative division within the state that functions similarly to a county, providing local government services and governance to its designated area.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.