Triple
T13182885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Bulgarian dialects |
E313772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern South Slavic dialect group |
C32594
|
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: Eastern South Slavic dialect group Context triple: [Eastern Bulgarian dialects, instanceOf, Eastern South Slavic dialect group]
-
A.
Slovene dialect group
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.
-
B.
South Slavic people
South Slavic people are an ethnolinguistic group in Southeast Europe who speak South Slavic languages and share related historical, cultural, and regional ties.
-
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.
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.
-
E.
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.
- F. None of above. chosen
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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:15 p.m.