Triple

T18407444
Position Surface form Disambiguated ID Type / Status
Subject Onega Lake section E441661 entity
Predicate connectsTo P845 FINISHED
Object Svir 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: Svir River | Statement: [Onega Lake section, connectsTo, Svir River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Svir River
Context triple: [Onega Lake section, connectsTo, Svir River]
  • A. Svir River chosen
    The Svir River is a waterway in northwestern Russia that links Lake Onega to Lake Ladoga and forms part of the Volga–Baltic waterway system.
  • B. Votka River
    The Votka River is a smaller watercourse in Russia that feeds into the larger Kama River within the Volga basin.
  • C. Votka River
    The Votka River is a minor river in Perm Krai, Russia, known as a right-bank tributary within the Siva River basin.
  • D. Vologda River
    The Vologda River is a waterway in northwestern Russia that flows through the city of Vologda and forms part of the region’s historical and economic transport network.
  • E. Vozha River
    The Vozha River is a waterway in western Russia historically notable as the site of a major 14th-century battle between the Grand Duchy of Moscow and the Golden Horde.
  • 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_69d8b9eb8a508190a942fd75ebd8b1dc completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e519591fdc8190a92f9587ec88478d completed April 19, 2026, 6:05 p.m.
Created at: April 10, 2026, 10:46 a.m.