Triple

T13432819
Position Surface form Disambiguated ID Type / Status
Subject Eastern Sámi languages E320154 entity
Predicate instanceOf P0 FINISHED
Object Sámi languages subgroup C13934 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 languages subgroup
Context triple: [Eastern Sámi languages, instanceOf, Sámi languages subgroup]
  • A. Sami language chosen
    Sami language is a group of closely related Uralic languages spoken by the Sami people across northern parts of Norway, Sweden, Finland, and Russia’s Kola Peninsula.
  • B. Munda languages subgroup
    The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
  • 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. 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.
  • E. 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.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
Created at: April 9, 2026, 9:40 p.m.