Triple

T1137408
Position Surface form Disambiguated ID Type / Status
Subject Tatar language E23170 entity
Predicate endonym P1435 FINISHED
Object татар теле E23170 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: татар теле | Statement: [Tatar language, endonym, татар теле]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: татар теле
Context triple: [Tatar language, endonym, татар теле]
  • A. Tatar language chosen
    The Tatar language is a Turkic language spoken primarily by Tatars in Russia and neighboring regions, with official status in Tatarstan and a literary tradition spanning several centuries.
  • B. Crimean Tatar language
    The Crimean Tatar language is a Turkic language traditionally spoken by the indigenous Crimean Tatar people of the Crimean Peninsula.
  • C. Turkmen language
    The Turkmen language is a Turkic language spoken primarily in Turkmenistan and surrounding regions, closely related to Turkish and other Oghuz languages.
  • D. Bashkir language
    The Bashkir language is a Turkic language spoken primarily by the Bashkir people in Russia, especially in the Republic of Bashkortostan.
  • E. Tajik language
    The Tajik language is a variety of Persian spoken primarily in Tajikistan and written in the Cyrillic script.
  • 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_69a493ec75988190b63a11bafaec29b4 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc2450c481909b9264e170070326 completed March 1, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac59ae5f20819093f8acc3ba7a6638 completed March 7, 2026, 5 p.m.
Created at: March 1, 2026, 7:44 p.m.