Triple
T5975147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Baltic languages |
E132967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Baltic languages |
C6283
|
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 the Baltic languages Context triple: [Western Baltic languages, instanceOf, branch of the Baltic languages]
-
A.
Baltic language
chosen
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.
-
B.
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.
-
C.
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.
-
D.
West Slavic languages
West Slavic languages are a subgroup of the Slavic language family, including Polish, Czech, Slovak, and related languages, primarily spoken in Central Europe and characterized by shared phonological, grammatical, and lexical features.
-
E.
branch of the Turkic languages
A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:04 p.m.