Triple

T18182764
Position Surface form Disambiguated ID Type / Status
Subject Vitebsk Region E435331 entity
Predicate containsRiver P165 FINISHED
Object Dnieper 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: Dnieper | Statement: [Vitebsk Region, containsRiver, Dnieper]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dnieper
Context triple: [Vitebsk Region, containsRiver, Dnieper]
  • A. Dnieper chosen
    The Dnieper is a major Eastern European river that flows through Russia, Belarus, and Ukraine before emptying into the Black Sea.
  • B. Taras River
    The Taras River is an ancient waterway in southern Italy historically associated with the Greek colony of Tarentum (modern Taranto) on the Ionian Sea.
  • C. Dniester
    The Dniester is a major river in Eastern Europe that flows through Ukraine and Moldova before emptying into the Black Sea.
  • D. Zbruch River
    The Zbruch River is a river in western Ukraine that historically served as a border between empires and now flows through regions including Ternopil Oblast before joining the Dniester.
  • E. Vorskla River
    The Vorskla River is a significant tributary of the Dnieper River in central Ukraine, known for its historical battle sites and role in regional ecology and transport.
  • 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dffc432c8190af53da5256dc476c completed April 19, 2026, 2 p.m.
Created at: April 10, 2026, 10:31 a.m.