Triple
T5601840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inuit languages |
E147137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eskimo–Aleut languages |
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 languages Context triple: [Inuit languages, instanceOf, Eskimo–Aleut languages]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Japonic languages
Japonic languages are a small language family native to Japan and nearby regions, including Japanese and the Ryukyuan languages, characterized by shared grammatical structures and historical origins.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:39 p.m.