Triple

T3001239
Position Surface form Disambiguated ID Type / Status
Subject Judeo-Iranian languages E81791 entity
Predicate hasPart P35 FINISHED
Object Judeo-Hamedani E11349 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-Hamedani | Statement: [Judeo-Iranian languages, hasPart, Judeo-Hamedani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judeo-Hamedani
Context triple: [Judeo-Iranian languages, hasPart, Judeo-Hamedani]
  • A. Judeo-Kermani
    Judeo-Kermani is a Jewish dialect of Persian traditionally spoken by Jewish communities from the Kerman region of Iran.
  • B. Kurmanji
    Kurmanji is the most widely spoken dialect of the Kurdish language, used primarily by Kurds across Turkey, Syria, Iraq, Iran, and the diaspora.
  • C. Nabulsi
    Nabulsi refers to a person or thing originating from the city of Nablus in the West Bank, often associated with its distinctive cheese and traditional soap.
  • D. Judeo-Persian chosen
    Judeo-Persian is a group of Persian dialects historically spoken and written by Jewish communities in Iran, typically using the Hebrew script and incorporating Hebrew and Aramaic elements.
  • E. Gilaki
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • 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.