Triple

T1301273
Position Surface form Disambiguated ID Type / Status
Subject Uralic languages E27768 entity
Predicate instanceOf P0 FINISHED
Object Uralic language family 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: Uralic language family
Context triple: [Uralic languages, instanceOf, Uralic language family]
  • 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. Finno-Ugric people
    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.
  • D. Northwest Caucasian language
    A Northwest Caucasian language is a member of a small family of indigenous languages spoken in the northwestern Caucasus region, characterized by complex consonant systems, minimal vowel inventories, and rich verbal morphology.
  • E. Paleo-European language
    A Paleo-European language is a hypothesized pre-Indo-European language or group of languages once spoken in prehistoric Europe, known primarily through substratum influences, place names, and limited archaeological and linguistic reconstruction.
  • 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_69a496d6682881909ba658f1c1e0e2b0 completed March 1, 2026, 7:43 p.m.
Created at: March 1, 2026, 7:51 p.m.