Triple
T31662381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cup’ik language |
E808035
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Alaskan Yupik language |
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: Central Alaskan Yupik language Context triple: [Cup’ik language, instanceOf, Central Alaskan Yupik language]
-
A.
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.
-
B.
Yup'ik language variety
chosen
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.
-
C.
Athabaskan–Eyak language
The Athabaskan–Eyak language is a reconstructed ancestral language hypothesized to be the common proto-language from which the Athabaskan and Eyak language families of North America descended.
-
D.
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.
-
E.
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.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:57 p.m.