Triple
T21194846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakhtiari Luri |
E522300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southwestern Iranian dialect |
C7624
|
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: Southwestern Iranian dialect Context triple: [Bakhtiari Luri, instanceOf, Southwestern Iranian dialect]
-
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.
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.
-
C.
branch of Iranian languages
chosen
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.
-
D.
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.
-
E.
Kurdish dialect
A Kurdish dialect is a regional or social variety of the Kurdish language characterized by distinct phonological, lexical, and grammatical features shared by a specific Kurdish-speaking community.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:08 p.m.