Triple
T33747437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urmia–Salamas cluster |
E864736
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | group of closely related dialects |
C5354
|
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: group of closely related dialects Context triple: [Urmia–Salamas cluster, instanceOf, group of closely related dialects]
-
A.
group of dialects
chosen
A group of dialects is a set of closely related language varieties that share common structural features and a historical or geographic connection within a larger language.
-
B.
group of English dialects
A group of English dialects is a collection of regionally or socially distinct varieties of the English language that share common linguistic features while differing in pronunciation, vocabulary, and grammar from other such groups.
-
C.
group of language varieties
A group of language varieties is a conceptual class encompassing related dialects, sociolects, or registers that share a common linguistic base but differ in systematic ways across regions, communities, or contexts.
-
D.
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.
-
E.
dialect continuum
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.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.