Triple
T15477131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | گیلکی |
E376810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | زبان ایرانی شمالغربی |
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: زبان ایرانی شمالغربی Context triple: [گیلکی, instanceOf, زبان ایرانی شمالغربی]
-
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.
branch of Iranian languages
A branch of Iranian languages is a subgroup within the Iranian language family comprising closely related languages that share a common historical origin, structural features, and geographic distribution.
-
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.
variety of Gorani language
A variety of Gorani language is a regional or social form of the Gorani speech continuum, distinguished by its own phonological, lexical, and grammatical features while remaining mutually intelligible with other Gorani varieties.
-
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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:34 a.m.