Triple

T685249
Position Surface form Disambiguated ID Type / Status
Subject Gorskie Yevrei E13270 entity
Predicate languageUsed P238 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: [Gorskie Yevrei, languageUsed, Judeo-Tat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Judeo-Tat
Context triple: [Gorskie Yevrei, languageUsed, 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. Chuvash
    Chuvash are a Turkic ethnic group native to the Volga region of Russia, known for their distinct Chuvash language and culture.
  • C. Ossetian language
    The Ossetian language is an Eastern Iranian language spoken primarily in the Caucasus region of Russia, especially in North and South Ossetia.
  • D. 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.
  • E. Seraiki
    Seraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a0924dec8190bbbd2bb244f85211 completed March 1, 2026, 8:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69a5dca153e081908facd835a79da25d completed March 2, 2026, 6:53 p.m.
Created at: March 1, 2026, 7:36 p.m.