Triple
T25823183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovene dialect continuum |
E650454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slavic dialect continuum |
C1720
|
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: Slavic dialect continuum Context triple: [Slovene dialect continuum, instanceOf, Slavic dialect continuum]
-
A.
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.
-
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.
dialect continuum
chosen
A dialect continuum is a range of geographically adjacent language varieties that change gradually from one area to the next, so that neighboring dialects are mutually intelligible but those at distant ends may not be.
-
D.
Slavic dialect
A Slavic dialect is a regional or social variety of a Slavic language characterized by distinct phonological, grammatical, and lexical features that differentiate it from the standard language and other dialects.
-
E.
Balkan Slavic dialects
Balkan Slavic dialects are a group of South Slavic vernaculars spoken in the Balkan Peninsula that share distinctive grammatical and phonological features shaped by intense contact with neighboring Balkan languages.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:31 a.m.