Triple
T4893259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dari |
E109613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the 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 the Persian language Context triple: [Dari, instanceOf, variety of the 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.
branch of Iranian languages
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.
-
C.
variety of the Greek language
A variety of the Greek language is a distinct form or dialect of Greek, characterized by specific phonological, grammatical, lexical, and pragmatic features used by a particular community or in a particular context.
-
D.
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.
-
E.
variety of Arabic
A variety of Arabic is a distinct form of the Arabic language, characterized by its own phonological, lexical, and grammatical features, typically associated with a particular region, community, or social context.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:28 p.m.