Triple

T8657697
Position Surface form Disambiguated ID Type / Status
Subject Siberian Governorate E205462 entity
Predicate capital P234 FINISHED
Object Tobolsk E526588 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: Tobolsk | Statement: [Siberian Governorate, capital, Tobolsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tobolsk
Context triple: [Siberian Governorate, capital, Tobolsk]
  • A. Tobolsk chosen
    Tobolsk is a historic Siberian town in Russia known for its Kremlin and as a place of exile and imprisonment during the late imperial period.
  • B. Irkutsk
    Irkutsk is a major city in southeastern Siberia, Russia, historically significant as a political and administrative center and a key hub during the Russian Civil War.
  • C. Nizhnevartovsk
    Nizhnevartovsk is a major oil-producing city in western Siberia, Russia, known as one of the centers of the country’s petroleum industry.
  • D. Ulan-Ude
    Ulan-Ude is the capital city of the Republic of Buryatia in Russia, known as a major cultural and political center of the Buryat people.
  • E. Severobaikalsk
    Severobaikalsk is a small town in northern Buryatia, Russia, located on the northern shore of Lake Baikal and serving as an important transport hub in eastern Siberia.
  • 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_69ca8350897c819086cde7596fbe5fe7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc486d576081908ad28749c7971432 completed March 31, 2026, 10:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69cfd070ca0c819092b98a7aa079c33c completed April 3, 2026, 2:36 p.m.
Created at: March 30, 2026, 6:30 p.m.