Triple

T17313127
Position Surface form Disambiguated ID Type / Status
Subject Saransk E420350 entity
Predicate officialLanguage P236 FINISHED
Object Erzya E149564 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: Erzya | Statement: [Saransk, officialLanguage, Erzya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Erzya
Context triple: [Saransk, officialLanguage, Erzya]
  • A. Erzya language chosen
    The Erzya language is a Uralic, Finno-Volgaic language spoken primarily by the Erzya Mordvin people in central Russia.
  • B. Ostyako-Vogulsk
    Ostyako-Vogulsk is the former name of Khanty-Mansiysk, a town in western Siberia that is now the administrative center of Russia’s Khanty-Mansi Autonomous Okrug.
  • C. Udmurts
    The Udmurts are a Finno-Ugric ethnic group native to the Volga-Ural region of Russia, known for their distinct Udmurt language, folklore, and traditional rural culture.
  • D. Chuvash
    Chuvash are a Turkic ethnic group native to the Volga region of Russia, known for their distinct Chuvash language and culture.
  • E. Ossetian language
    The Ossetian language is an Eastern Iranian language spoken primarily in the Caucasus region of Russia, especially in North and South Ossetia.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4399a4194819091d34cd3fffc8072 completed April 19, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180e6e830819097b33d6b99232727 completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:43 a.m.