Triple

T2103068
Position Surface form Disambiguated ID Type / Status
Subject World War I poetry E37132 entity
Predicate hasLanguage P15 FINISHED
Object Tatar 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: Tatar | Statement: [World War I poetry, hasLanguage, Tatar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tatar
Context triple: [World War I poetry, hasLanguage, Tatar]
  • 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. Bashkir
    Bashkir is a Turkic language spoken primarily by the Bashkir people in Russia’s Republic of Bashkortostan and surrounding regions.
  • C. Siberian Tatar language
    The Siberian Tatar language is a Turkic language spoken by Siberian Tatars in western Siberia, characterized by features of the Kipchak branch and influences from neighboring Siberian peoples and Russian.
  • D. Chuvash
    Chuvash are a Turkic ethnic group native to the Volga region of Russia, known for their distinct Chuvash language and culture.
  • E. Bashkir language
    The Bashkir language is a Turkic language spoken primarily by the Bashkir people in Russia, especially in the Republic of Bashkortostan.
  • 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_69a8861828948190924aa30c08806b3a completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abbabe1e9081908ea66c5406e2f1d9 completed March 7, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae5d8bffd0819095629956f9584222 completed March 9, 2026, 5:41 a.m.
Created at: March 4, 2026, 7:43 p.m.