Triple

T1302332
Position Surface form Disambiguated ID Type / Status
Subject Germanic peoples E27794 entity
Predicate instanceOf P0 FINISHED
Object Indo-European peoples C5749 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: Indo-European peoples
Context triple: [Germanic peoples, instanceOf, Indo-European peoples]
  • A. 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.
  • B. 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.
  • C. Indo-Aryan people chosen
    Indo-Aryan people are a diverse group of ethnolinguistic communities in South Asia who speak Indo-Aryan languages, a major branch of the Indo-European language family, and share related historical and cultural roots.
  • D. 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.
  • E. Indo-European language
    An Indo-European language is a member of a large family of related languages spoken across Europe and parts of Asia, all descended from a common prehistoric ancestor known as Proto-Indo-European.
  • 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.