Triple
T1194315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Iranian languages |
E25632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-European language branch |
C7357
|
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 language branch Context triple: [Indo-Iranian languages, instanceOf, Indo-European language branch]
-
A.
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.
-
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.
branch of the Germanic languages
A branch of the Germanic languages is a subgroup of related Germanic languages that share a common historical origin, structural features, and vocabulary, such as the North, West, or (extinct) East Germanic branches.
-
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.
West Germanic language
A West Germanic language is a member of the Germanic branch of the Indo-European language family that evolved in western and central Europe, including languages such as English, German, and Dutch.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:46 p.m.