Triple
T15477181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galeshi (Rudbari) dialect |
E376811
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Gilaki |
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: regional variety of Gilaki Context triple: [Galeshi (Rudbari) dialect, instanceOf, regional variety of Gilaki]
-
A.
regional variety of Azerbaijani
A regional variety of Azerbaijani is a geographically or socially localized form of the Azerbaijani language characterized by distinct phonological, lexical, and sometimes grammatical features.
-
B.
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.
-
C.
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.
-
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.
regional variety of Polish
A regional variety of Polish is a geographically localized form of the Polish language characterized by distinct pronunciation, vocabulary, and sometimes grammar that reflect the cultural and historical influences of a specific area.
- 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.