Triple
T23883487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lezgin |
E600269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lezgic language |
C48168
|
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: Lezgic language Context triple: [Lezgin, instanceOf, Lezgic language]
-
A.
regional variety of Lezgian
A regional variety of Lezgian is a geographically distinct form of the Lezgian language characterized by unique phonological, lexical, and grammatical features shared by speakers in a particular area.
-
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.
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.
-
D.
Caspian language
A Caspian language is any of several closely related Northwestern Iranian languages spoken along the southern coast of the Caspian Sea, characterized by shared phonological and grammatical features distinct from standard Persian.
-
E.
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.
- F. None of above. chosen
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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:24 p.m.