Triple

T21354749
Position Surface form Disambiguated ID Type / Status
Subject Tobolsk E526588 entity
Predicate namedAfter P63 FINISHED
Object Tobol River 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: Tobol River | Statement: [Tobolsk, namedAfter, Tobol River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tobol River
Context triple: [Tobolsk, namedAfter, Tobol River]
  • A. Tobol River chosen
    The Tobol River is a significant river in Western Siberia and northern Kazakhstan that flows through Russia and Kazakhstan before joining the Ob River.
  • B. Chulym River
    The Chulym River is a significant waterway in southwestern Siberia, Russia, flowing through the Tomsk and Krasnoyarsk regions before joining the Ob River.
  • C. Tobol’skaya Tura River
    The Tobol’skaya Tura River is a significant Siberian waterway that feeds into the Tobol River, contributing to the larger Ob–Irtysh river system in Russia.
  • D. Bolshaya Kokshaga River
    The Bolshaya Kokshaga River is a significant waterway in central Russia that flows through the Mari El Republic before emptying into the Volga River.
  • E. Azat River
    The Azat River is a notable river in central Armenia that flows through scenic gorges and supports nearby communities and agriculture.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8af9be3a48190aa8e6e9a5b812981 completed April 22, 2026, 11:23 a.m.
Created at: April 16, 2026, 5:06 p.m.