Triple
T33156749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daronta Pashayi |
E848598
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Pashayi |
C60208
|
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 Pashayi Context triple: [Daronta Pashayi, instanceOf, regional variety of Pashayi]
-
A.
Pashayi dialect
chosen
Pashayi dialect is a regional linguistic variety of the Pashayi language spoken primarily in eastern Afghanistan, characterized by distinct phonological, lexical, and grammatical features that differentiate it from other Pashayi varieties.
-
B.
regional variety of Ormuri
A regional variety of Ormuri is a geographically localized form of the Ormuri language characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area.
-
C.
regional variety of Ghomalaʼ
A regional variety of Ghomalaʼ is a geographically localized dialect of the Ghomalaʼ language characterized by distinct phonological, lexical, or syntactic features specific to a particular area or community.
-
D.
regional variety of the Shor language
A regional variety of the Shor language is a geographically distinct form of Shor characterized by specific phonological, lexical, and grammatical features shared by speakers in a particular area.
-
E.
regional variety of Garhwali
A regional variety of Garhwali is a localized form of the Garhwali language distinguished by its unique phonological, lexical, and syntactic features specific to a particular area within the Garhwal region.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.