Triple

T348540
Position Surface form Disambiguated ID Type / Status
Subject Mizrahi Jews E6992 entity
Predicate languageTradition P6149 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: [Mizrahi Jews, languageTradition, Judeo-Tat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judeo-Tat
Context triple: [Mizrahi Jews, languageTradition, 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. Ossetian language
    The Ossetian language is an Eastern Iranian language spoken primarily in the Caucasus region of Russia, especially in North and South Ossetia.
  • C. Gorani
    Gorani is a Northwestern Iranian language variety traditionally spoken by Kurdish communities in parts of Iran and Iraq, notable for its rich literary and religious heritage.
  • D. Seraiki
    Seraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • E. Rusyn language
    The Rusyn language is an East Slavic minority language spoken by Rusyn communities in Central and Eastern Europe, particularly in parts of Ukraine, Slovakia, Poland, and Serbia.
  • 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_69a2e7951ba08190960e90823b5078f3 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eb1c1c908190b3a01de893207ed1 completed Feb. 28, 2026, 1:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3dd31c720819092af1eb26bd3080a completed March 1, 2026, 6:31 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.