Triple
T15286290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Common Slavic |
E365408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Common Slavic dialect |
C33933
|
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: Common Slavic dialect Context triple: [Northern Common Slavic, instanceOf, Common Slavic dialect]
-
A.
Slavic dialect
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Eastern South Slavic dialect group
The Eastern South Slavic dialect group comprises the continuum of closely related Slavic dialects spoken primarily in Bulgaria and North Macedonia, forming the basis of the Bulgarian and Macedonian standard 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:15 a.m.