Triple

T3031111
Position Surface form Disambiguated ID Type / Status
Subject Ter Sámi E82896 entity
Predicate instanceOf P0 FINISHED
Object Samic 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: Samic language
Context triple: [Ter Sámi, instanceOf, Samic language]
  • A. 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.
  • B. 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.
  • 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. 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.
  • E. Samoyedic people
    Samoyedic people are a group of indigenous peoples of northern Eurasia, primarily in northern Russia, who speak Samoyedic languages of the Uralic family and traditionally practice reindeer herding, fishing, and hunting in Arctic and subarctic environments.
  • 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_69ad8b21a62881908ec5dd4fba4a187c completed March 8, 2026, 2:43 p.m.
Created at: March 8, 2026, 3:01 p.m.