Triple
T4976194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judeo-Tajik |
E111770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Judeo-Persian language variety |
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 language variety Context triple: [Judeo-Tajik, instanceOf, Judeo-Persian language variety]
-
A.
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.
-
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.
Semitic language
A Semitic language is a member of a family of related languages originating in the Middle East and North Africa, characterized by root-based morphology and including languages such as Arabic, Hebrew, and Amharic.
-
D.
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.
-
E.
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.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:33 p.m.