Triple

T31236749
Position Surface form Disambiguated ID Type / Status
Subject Mansi E796445 entity
Predicate instanceOf P0 FINISHED
Object Uralic-speaking people C4825 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: Uralic-speaking people
Context triple: [Mansi, instanceOf, Uralic-speaking people]
  • A. Finno-Ugric people chosen
    Finno-Ugric people are a group of ethnolinguistic populations in Northern and Eastern Europe and Western Siberia who speak Finno-Ugric languages, including Finns, Estonians, and various Uralic-speaking minorities such as the Sami, Mari, and Udmurts.
  • B. 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.
  • C. 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.
  • D. Northeast Caucasian people
    Northeast Caucasian people are an ethnolinguistic group indigenous to the northeastern Caucasus region, encompassing diverse communities such as Chechens, Avars, and Lezgins who share related Northeast Caucasian languages and cultural traditions.
  • E. Slavic people
    Slavic people are an ethnolinguistic group of Indo-European origin whose diverse nations and cultures across Eastern, Central, and Southeastern Europe share related Slavic languages and historical roots.
  • 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_69f224db69ac81909a370adad6a7ac7c completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 9:11 p.m.