Triple
T1679894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Slavic languages |
E36314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Slavic languages |
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: branch of Slavic languages Context triple: [East Slavic languages, instanceOf, branch of Slavic languages]
-
A.
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.
-
B.
Indo-European language branch
chosen
The Indo-European language branch is a major subgroup within the Indo-European language family comprising closely related languages that share a common ancestral origin and distinctive linguistic features.
-
C.
West Slavic people
West Slavic people are a subgroup of Slavic ethnic groups originating in Central Europe, primarily including Poles, Czechs, and Slovaks, who share related languages, cultural traditions, and historical development.
-
D.
Baltic language
A Baltic language is a member of the Indo-European language family spoken primarily around the eastern coast of the Baltic Sea, characterized by conservative grammatical features and rich inflectional morphology.
-
E.
branch of Iranian languages
A branch of Iranian languages is a subgroup within the Iranian language family comprising closely related languages that share a common historical origin, structural features, and geographic distribution.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:29 p.m.