Triple
T3185992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurgan hypothesis |
E66699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theory of Indo-European origins |
C12410
|
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: theory of Indo-European origins Context triple: [Kurgan hypothesis, instanceOf, theory of Indo-European origins]
-
A.
Indo-Europeanist
An Indo-Europeanist is a scholar who studies the Indo-European language family, including its historical development, comparative grammar, and reconstruction of its proto-language and related cultures.
-
B.
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.
-
C.
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.
-
D.
Indo-European religion
Indo-European religion refers to the reconstructed set of mythological beliefs, rituals, and deities shared by the ancient peoples speaking Proto-Indo-European languages, inferred from common patterns across their descendant traditions.
-
E.
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.
- F. None of above. chosen
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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.