Triple
T35760941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern South Slavic languages |
E1033567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slavic languages subgroup |
C32812
|
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 languages subgroup Context triple: [Eastern South Slavic languages, instanceOf, Slavic languages subgroup]
-
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.
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.
-
D.
Balkan Slavic dialects
chosen
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.
-
E.
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.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.