Triple

T651306
Position Surface form Disambiguated ID Type / Status
Subject Judeo-Persian E11349 entity
Predicate hasDialect P4251 FINISHED
Object Judeo-Isfahani 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-Isfahani | Statement: [Judeo-Persian, hasDialect, Judeo-Isfahani]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judeo-Isfahani
Context triple: [Judeo-Persian, hasDialect, Judeo-Isfahani]
  • A. 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.
  • B. Gilaki
    Gilaki is an Iranian language spoken primarily in Iran’s Gilan Province along the Caspian Sea coast.
  • C. Judeo-Arabic
    Judeo-Arabic is a group of Arabic dialects historically spoken and written by Jewish communities, typically using the Hebrew script and incorporating Hebrew and Aramaic elements.
  • D. Judeo-Kermani
    Judeo-Kermani is a Jewish dialect of Persian traditionally spoken by Jewish communities from the Kerman region of Iran.
  • E. Nusach Sefard
    Nusach Sefard is a liturgical rite and prayer text tradition used primarily by Hasidic and some Sephardic-influenced Ashkenazi Jewish communities.
  • 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_69a493266a2881909daf4c40f719dee8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49f33b6d881908b6662b73d6fe833 completed March 1, 2026, 8:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69a66d8cd1e481908b77e4db0b6681bf completed March 3, 2026, 5:11 a.m.
Created at: March 1, 2026, 7:36 p.m.