Triple

T18392801
Position Surface form Disambiguated ID Type / Status
Subject Svir E449778 entity
Predicate hasLeftTributary P415 FINISHED
Object Vazhinka 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: Vazhinka River | Statement: [Svir, hasLeftTributary, Vazhinka River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vazhinka River
Context triple: [Svir, hasLeftTributary, Vazhinka River]
  • A. Vazhinka River chosen
    The Vazhinka River is a smaller watercourse in northwestern Russia that feeds into the Svir River as one of its tributaries.
  • B. Kovzha River
    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.
  • C. Ruzhanka River
    The Ruzhanka River is a small river in western Belarus that flows through the town of Ruzhany and forms part of the local natural and historical landscape.
  • D. 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.
  • E. Strumitsa River
    The Strumitsa River is a river in North Macedonia and Bulgaria that flows through the town of Strumica before joining the Struma River.
  • 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.