Triple

T2983711
Position Surface form Disambiguated ID Type / Status
Subject Inari Sámi E80571 entity
Predicate instanceOf P0 FINISHED
Object Sámi language C3812 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: Sámi language
Context triple: [Inari Sámi, instanceOf, Sámi language]
  • A. Finnic language
    A Finnic language is a member of the Uralic language family spoken primarily around the Baltic Sea region, including languages such as Finnish, Estonian, and Karelian, characterized by agglutinative morphology and vowel harmony.
  • B. Uralic language chosen
    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.
  • C. 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.
  • D. West Nordic language
    A West Nordic language is a North Germanic language variety spoken in the western Nordic region, primarily including Icelandic, Faroese, and sometimes Norwegian dialects with shared historical and structural features.
  • E. Baltic language
    A Baltic language is a member of the Indo-European language family spoken primarily around the eastern coast of the Baltic Sea, characterized by conservative grammatical features and rich inflectional morphology.
  • 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_69ad8b15f6ac8190be5fd16a33edcb4f completed March 8, 2026, 2:43 p.m.
Created at: March 8, 2026, 2:59 p.m.