Triple

T22481591
Position Surface form Disambiguated ID Type / Status
Subject Kipchak–Bulgar group E555777 entity
Predicate exemplifiedBy P1259 FINISHED
Object Mishar Tatar NE NERFINISHED

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: Mishar Tatar | Statement: [Kipchak–Bulgar group, exemplifiedBy, Mishar Tatar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mishar Tatar
Context triple: [Kipchak–Bulgar group, exemplifiedBy, Mishar Tatar]
  • A. Mishar Tatar chosen
    Mishar Tatar is a major dialect of the Tatar language spoken primarily by the Mishar Tatars in parts of Russia and neighboring regions.
  • B. Maychew
    Maychew is a town in northern Ethiopia known as a local commercial and administrative center within the Tigray highlands.
  • C. Taras
    Taras is the ancient Greek city in southern Italy that later became known by its Roman name Tarentum.
  • D. Taras
    Taras is a masculine given name of Slavic origin, most famously borne by the Ukrainian poet and national figure Taras Shevchenko.
  • E. Czeremcha
    Czeremcha is a village in northeastern Poland that serves as a local railway junction and border-area transport hub near Belarus.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e53897c819088863779f8c50bb0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15c397b248190b36c2fbfa6489693 completed April 29, 2026, 1:17 a.m.
Created at: April 16, 2026, 8:49 p.m.