Triple
T35906517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Lechitic |
E1038486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of West Slavic languages |
C10813
|
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 West Slavic languages Context triple: [Southern Lechitic, instanceOf, branch of West Slavic languages]
-
A.
West Slavic languages
chosen
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.
-
B.
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.
-
C.
branch of Western Bismarck languages
A branch of Western Bismarck languages is a subgroup of related Oceanic languages spoken in the western Bismarck Archipelago that share common historical origins and linguistic features.
-
D.
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.
-
E.
Slavic dialect grouping
A Slavic dialect grouping is a conceptual class that organizes related Slavic language varieties into clusters based on shared phonological, grammatical, and lexical features reflecting common historical development and geographic proximity.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.