Triple
T3001235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judeo-Iranian languages |
E81791
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Judeo-Tat |
E6990
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Judeo-Tat | Statement: [Judeo-Iranian languages, hasPart, Judeo-Tat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Judeo-Tat Context triple: [Judeo-Iranian languages, hasPart, Judeo-Tat]
-
A.
Judeo-Tat
chosen
Judeo-Tat is a Southwest Iranian Jewish language traditionally spoken by Mountain Jews of the eastern Caucasus region.
-
B.
Karaim language
The Karaim language is a severely endangered Turkic language historically spoken by the Karaim people, primarily in Lithuania, Poland, and Crimea, reflecting a unique blend of Turkic, Hebrew, and local linguistic influences.
-
C.
Judeo-Kermani
Judeo-Kermani is a Jewish dialect of Persian traditionally spoken by Jewish communities from the Kerman region of Iran.
-
D.
Dargin
Dargin is a Northeast Caucasian language spoken primarily by the Dargin people in the Republic of Dagestan in Russia.
-
E.
Tsakhur language
The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1022e48190afee77db94635ff2 |
completed | March 8, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b12e4b54188190bf900bf10061a57a |
completed | March 11, 2026, 8:56 a.m. |
Created at: March 8, 2026, 2:59 p.m.