Triple

T4473752
Position Surface form Disambiguated ID Type / Status
Subject Volga–Baltic Waterway E98556 entity
Predicate hasPart P35 FINISHED
Object Kovzha River E527376 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: Kovzha River | Statement: [Volga–Baltic Waterway, hasPart, Kovzha River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Kovzha River
Context triple: [Volga–Baltic Waterway, hasPart, Kovzha River]
  • A. Kovzha River chosen
    The Kovzha River is a waterway in northwestern Russia that forms part of the navigable route linking the Volga River basin with the Baltic Sea.
  • B. Vokhma River
    The Vokhma River is a smaller watercourse in Russia that serves as one of the tributaries feeding into the larger Vetluga River system.
  • C. Pchyovzha River
    The Pchyovzha River is a smaller watercourse in northwestern Russia that serves as one of the tributaries feeding into the Volkhov River system.
  • D. Sogozha River
    The Sogozha River is a waterway in Russia that serves as one of the tributaries feeding the Rybinsk Reservoir, an important artificial lake on the Volga River system.
  • E. Zusha River
    The Zusha River is a significant waterway in western Russia that feeds into the Oka River and contributes to its drainage basin.
  • 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_69b3454b4ae481908967426dd37284d6 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356b95c888190a84bf4a9b2c60aa6 completed March 13, 2026, 12:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69bfe8ba08f88190a0b10b7a0a05b98c completed March 22, 2026, 1:03 p.m.
Created at: March 12, 2026, 11:35 p.m.