Triple
T4455546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzhidi |
E97712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Judeo-Persian dialect |
C14735
|
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: Judeo-Persian dialect Context triple: [Dzhidi, instanceOf, Judeo-Persian dialect]
-
A.
Jewish dialect
chosen
A Jewish dialect is a variety of a language shaped by the historical, religious, and cultural experiences of Jewish communities, often incorporating Hebrew or Aramaic elements and distinct phonological, lexical, and syntactic features.
-
B.
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.
-
C.
Elamite language
Elamite language is an extinct language isolate once spoken in the ancient kingdom of Elam in what is now southwestern Iran, known primarily from cuneiform inscriptions dating from the 3rd to 1st millennia BCE.
-
D.
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.
-
E.
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.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:33 p.m.