Triple
T21258772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Mazanderani |
E523940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mazanderani dialect |
C5771
|
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: Mazanderani dialect Context triple: [Central Mazanderani, instanceOf, Mazanderani dialect]
-
A.
Northwest Iranian language
chosen
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.
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.
-
C.
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.
-
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.
Pamir language
The Pamir language is a group of Eastern Iranian languages spoken in the high-mountain Pamir region of Tajikistan, Afghanistan, and surrounding areas, characterized by significant diversity and archaic linguistic 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:59 p.m.