Triple
T21138636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Asian Persian dialects |
E520875
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Persian dialect continuum |
C1720
|
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: Persian dialect continuum Context triple: [Central Asian Persian dialects, instanceOf, Persian dialect continuum]
-
A.
Northwest Iranian language
A Northwest Iranian language is a member of the western branch of the Iranian languages spoken primarily in regions of northwestern Iran and neighboring areas, characterized by shared phonological, lexical, and grammatical features distinct from Southwest Iranian languages.
-
B.
Zaza–Gorani language
The Zaza–Gorani language is a proposed grouping of two closely related Northwestern Iranian languages, Zaza and Gorani, spoken primarily by ethnic Kurdish and related communities in eastern Turkey, northern Iraq, and western Iran.
-
C.
Shastan language
The Shastan language is a group of closely related, now mostly extinct Native American languages once spoken by the Shasta and neighboring peoples of northern California and southern Oregon.
-
D.
Tabasaran dialect
Tabasaran dialect is a regional or social variety of the Tabasaran language, distinguished by specific phonological, lexical, and grammatical features used by particular speaker communities.
-
E.
dialect continuum
chosen
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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:57 p.m.