Triple
T4107599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judeo-Kermani |
E88491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Iranian Jewish language variety |
C7624
|
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: Iranian Jewish language variety Context triple: [Judeo-Kermani, instanceOf, Iranian Jewish 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
chosen
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.
regional variety of Azerbaijani
A regional variety of Azerbaijani is a geographically or socially localized form of the Azerbaijani language characterized by distinct phonological, lexical, and sometimes grammatical features.
-
D.
variety of Persian
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.
-
E.
Iranian people
Iranian people are a diverse ethnic and national group primarily associated with Iran, sharing historical, linguistic, and cultural ties rooted in the broader Iranian (Persian) civilization.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:40 p.m.