Triple

T22197903
Position Surface form Disambiguated ID Type / Status
Subject Turkic scripts E548593 entity
Predicate usedForLanguage P907 FINISHED
Object Bashkir 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: Bashkir | Statement: [Turkic scripts, usedForLanguage, Bashkir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bashkir
Context triple: [Turkic scripts, usedForLanguage, Bashkir]
  • A. Bashkir chosen
    Bashkir is a Turkic language spoken primarily by the Bashkir people in Russia’s Republic of Bashkortostan and surrounding regions.
  • B. Bashkirs
    The Bashkirs are a Turkic ethnic group native to the Volga-Ural region of Russia, known for their distinct language, culture, and historical role in the area.
  • C. Kalmyk
    Kalmyk refers to a Mongolic ethnic group primarily living in Russia’s Kalmykia region, known for being the only traditionally Buddhist people in Europe.
  • D. Komi
    Komi is a traditional village on the Greek island of Tinos, known for its Cycladic architecture and rural charm.
  • E. Komi
    The Komi are a Finno-Ugric ethnic group indigenous to northern European Russia, known for their distinct Uralic language and traditional presence in regions such as the Komi Republic and surrounding areas.
  • 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_69e11e3ecc7c8190b5f94cd8f42e9d37 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12ae8c74c819080c7f9e8383ecaa7 completed April 28, 2026, 9:47 p.m.
Created at: April 16, 2026, 8:36 p.m.