Triple

T18392786
Position Surface form Disambiguated ID Type / Status
Subject Svir E449778 entity
Predicate hasLock P2431 FINISHED
Object Upper Svir Lock 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: Upper Svir Lock | Statement: [Svir, hasLock, Upper Svir Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Upper Svir Lock
Context triple: [Svir, hasLock, Upper Svir Lock]
  • A. Upper Svir Lock chosen
    Upper Svir Lock is a navigation lock on Russia’s Svir River that enables vessels to bypass a section of the river’s elevation change as part of the inland waterway system.
  • B. Lower Svir Lock
    Lower Svir Lock is a major navigation lock on Russia’s Svir River that enables vessel passage and water level control along this key inland waterway.
  • C. Cheboksary Dam lock
    Cheboksary Dam lock is a navigation facility that enables vessels to pass through the Cheboksary hydroelectric dam on the Volga River in Russia.
  • D. Mozhaysk Dam
    Mozhaysk Dam is a hydraulic structure in Russia that impounds the Mozhaysk Reservoir, serving regional water supply, flood control, and related purposes.
  • E. Votkinsk Dam
    Votkinsk Dam is a major hydroelectric dam on the Kama River in Russia, integral to regional power generation and water management.
  • 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_69d8b9fab8a8819086a9ddc0871715e0 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e518435cf481908393c1eb2b4ba659 completed April 19, 2026, 6 p.m.
Created at: April 10, 2026, 10:46 a.m.