Triple

T17265727
Position Surface form Disambiguated ID Type / Status
Subject Обь E419121 entity
Predicate имеетГородНаБерегу P969 FINISHED
Object Сургут E490651 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: Сургут | Statement: [Обь, имеетГородНаБерегу, Сургут]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Сургут
Context triple: [Обь, имеетГородНаБерегу, Сургут]
  • A. Surgut chosen
    Surgut is a major oil-producing city in western Siberia, Russia, known as an important industrial and transportation hub in the Khanty-Mansi Autonomous Okrug.
  • B. Tyumen
    Tyumen is a historic city in western Siberia, Russia, known as an early Russian settlement in Siberia and now a major industrial and administrative center.
  • 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. Salekhard
    Salekhard is a Russian Arctic city located on the Ob River and notable as the only city in the world situated directly on the Arctic Circle.
  • E. Krasnoyarsk
    Krasnoyarsk is a large industrial and cultural city in central Russia, situated on the Yenisei River and known as one of the key urban centers of 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_69d886d9ab108190b70edd8d17aa1204 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42f44ec7c81909a925fc8692b0a6c completed April 19, 2026, 1:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0195488d2c81908ac6c19f54f61796 completed May 11, 2026, 8:37 a.m.
Created at: April 10, 2026, 5:40 a.m.