Triple
T22671125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudovian language |
E560218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Baltic language |
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: Western Baltic language Context triple: [Sudovian language, instanceOf, Western Baltic language]
-
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.
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.
-
C.
West Nordic language
A West Nordic language is a North Germanic language variety spoken in the western Nordic region, primarily including Icelandic, Faroese, and sometimes Norwegian dialects with shared historical and structural features.
-
D.
Baltic German
A Baltic German is a member of the historically German-speaking minority that lived in the Baltic region (primarily present-day Estonia and Latvia), often forming part of the local urban elite and nobility from medieval times until the 20th century.
-
E.
Eastern Romance language
An Eastern Romance language is a member of the Romance branch of the Indo-European language family that evolved from Eastern varieties of Vulgar Latin, primarily spoken in the Balkans and surrounding regions.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:10 p.m.