Triple
T23483302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Persian |
E570463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Persian language |
C5231
|
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: variety of Persian language Context triple: [Eastern Persian, instanceOf, variety of Persian language]
-
A.
variety of Persian
chosen
A variety of Persian is a distinct form or dialect of the Persian language characterized by unique phonological, lexical, and grammatical features associated with a particular region, community, or social group.
-
B.
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.
-
C.
variety of Tajik language
A variety of Tajik language is a regional or social form of Tajik distinguished by specific phonological, lexical, and grammatical features while remaining mutually intelligible with other forms of Tajik.
-
D.
variety of Tabasaran language
A variety of the Tabasaran language is a regional or social form of Tabasaran distinguished by systematic differences in pronunciation, vocabulary, or grammar within the broader Tabasaran linguistic continuum.
-
E.
variety of Lezgian language
A variety of the Lezgian language is a regional or social form of Lezgian distinguished by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other forms.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:03 p.m.