Triple

T12212936
Position Surface form Disambiguated ID Type / Status
Subject Mordovia E291009 entity
Predicate capital P234 FINISHED
Object Saransk E420350 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: Saransk | Statement: [Mordovia, capital, Saransk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saransk
Context triple: [Mordovia, capital, Saransk]
  • A. Saransk chosen
    Saransk is the capital city of the Republic of Mordovia in western Russia, known as an administrative, cultural, and industrial center of the region.
  • B. Shadrinsk
    Shadrinsk is a town in Kurgan Oblast, Russia, known as an industrial and cultural center in the southern Ural region.
  • C. Nevyansk
    Nevyansk is a historic town in Russia’s Ural region, best known for its 18th-century Leaning Tower of Nevyansk and its role in early Russian industrial development.
  • D. Pervouralsk
    Pervouralsk is an industrial city in Russia’s Ural region, known for its metallurgical plants and location near the geographic border between Europe and Asia.
  • E. Kholm
    Kholm is a historic town in eastern Poland, known today as Chełm, with medieval roots and significance in the history of the Kingdom of Galicia–Volhynia.
  • 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_69d6ab65923081909acfc61b7a612233 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91c915f548190b34a743f0a3bb51a completed April 10, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60a9f45108190a814cdca52e77b5e completed May 2, 2026, 2:30 p.m.
Created at: April 8, 2026, 9:51 p.m.