Triple

T23050874
Position Surface form Disambiguated ID Type / Status
Subject Udmurt ASSR E574007 entity
Predicate majorCity P316 FINISHED
Object Sarapul 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: Sarapul | Statement: [Udmurt ASSR, majorCity, Sarapul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sarapul
Context triple: [Udmurt ASSR, majorCity, Sarapul]
  • A. Sarapul chosen
    Sarapul is a historic city in Russia’s Udmurt Republic, known as a regional industrial and transport center on the eastern edge of European Russia.
  • B. Yuzovka
    Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
  • C. Yalutorovsk
    Yalutorovsk is a historic town in western Siberia, Russia, known for its 17th-century origins as a fortress settlement and its location on the Tobol River.
  • D. Petrovskoye
    Petrovskoye was the original Russian fortress settlement that later developed into the modern city of Makhachkala in Dagestan, Russia.
  • E. Shadrinsk
    Shadrinsk is a town in Kurgan Oblast, Russia, known as an industrial and cultural center in the southern Ural region.
  • 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_69e245b9c11481909d06c872214d21af completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1867c443081909588262bc90748af completed April 29, 2026, 4:18 a.m.
Created at: April 17, 2026, 3:54 p.m.