Triple
T2947323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inuktun |
E79533
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eskimo–Aleut language variety |
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: Eskimo–Aleut language variety Context triple: [Inuktun, instanceOf, Eskimo–Aleut language variety]
-
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.
indigenous North American language family
A broad grouping of related indigenous languages spoken by Native peoples across North America, defined by shared historical origins and structural features.
-
D.
Uralic language
A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
-
E.
Malayo-Polynesian language
A Malayo-Polynesian language is a member of a large branch of the Austronesian language family spoken across Southeast Asia, Madagascar, and the Pacific islands, characterized by shared 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.