Triple
T9581026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Yupik |
E231169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yupik language ancestor |
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: Yupik language ancestor Context triple: [Proto-Yupik, instanceOf, Yupik language ancestor]
-
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.
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.
-
C.
Hokan language
Hokan language is a proposed but controversial grouping of several Native American language families and isolates of western North America, hypothesized to share a distant common ancestor.
-
D.
Tungusic language
A Tungusic language is a member of a small family of agglutinative languages spoken primarily in eastern Siberia, northeastern China, and the Russian Far East by Tungusic peoples.
-
E.
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.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:05 p.m.