Triple
T35764900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western South Slavic languages |
E1033988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of South Slavic languages |
C20955
|
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: subgroup of South Slavic languages Context triple: [Western South Slavic languages, instanceOf, subgroup of South Slavic languages]
-
A.
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.
-
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.
Balkan language
A Balkan language is any language spoken in the Balkan Peninsula that often shares grammatical and lexical features with neighboring tongues due to long-term contact and convergence.
-
D.
Slovene dialect group
chosen
A Slovene dialect group is a classification of closely related regional varieties of the Slovene language that share common phonological, morphological, syntactic, and lexical features.
-
E.
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.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.