Triple

T5181997
Position Surface form Disambiguated ID Type / Status
Subject Daugavpils E116942 entity
Predicate locatedOnRiver P165 FINISHED
Object Daugava River E28573 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: Daugava River | Statement: [Daugavpils, locatedOnRiver, Daugava River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Daugava River
Context triple: [Daugavpils, locatedOnRiver, Daugava River]
  • A. Daugava River chosen
    The Daugava River is a major Eastern European river flowing through Russia, Belarus, and Latvia before emptying into the Baltic Sea.
  • B. Western Dvina River
    The Western Dvina River, also known as the Daugava, is a major Eastern European river flowing from Russia through Belarus and Latvia into the Baltic Sea.
  • C. Northern Dvina River
    The Northern Dvina River is a major waterway in northwestern Russia that flows into the White Sea and has long served as an important route for trade and transport.
  • D. Neman River
    The Neman River is a major river in Eastern Europe that flows through Belarus and Lithuania before emptying into the Baltic Sea.
  • E. Narva River
    The Narva River is a major river in northeastern Europe that forms part of the border between Estonia and Russia, flowing from Lake Peipus into the Baltic Sea.
  • 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_69bd446140f08190becb93c61158f27f completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd799bc58c819098a8e91e21baaef4 completed March 20, 2026, 4:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69bef7f6b98c8190bbc4f123560d32f4 completed March 21, 2026, 7:56 p.m.
Created at: March 20, 2026, 1:45 p.m.