Triple
T25698888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barzani Jewish Neo-Aramaic |
E644401
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish Neo-Aramaic dialect |
C26984
|
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: Jewish Neo-Aramaic dialect Context triple: [Barzani Jewish Neo-Aramaic, instanceOf, Jewish Neo-Aramaic dialect]
-
A.
Jewish dialect
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.
modern vernacular form of Neo-Aramaic
chosen
A modern vernacular form of Neo-Aramaic is a contemporary spoken descendant of the Aramaic language, used as a native or community language by specific ethnic or religious groups and characterized by regional phonological, lexical, and grammatical innovations.
-
C.
Western Aramaic varieties
Western Aramaic varieties are the group of Aramaic dialects historically spoken in the western Levant, of which only a few modern dialects in Syria survive today.
-
D.
Luri dialect
Luri dialect is a regional variety of the Luri language, spoken by the Lur people of western and southwestern Iran, characterized by distinct phonological, lexical, and grammatical features that differentiate it from standard Persian and other Iranian languages.
-
E.
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.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:41 p.m.