Triple

T1768948
Position Surface form Disambiguated ID Type / Status
Subject Dnipro E38828 entity
Predicate locatedOnRiver P165 FINISHED
Object Dnieper River E41855 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: Dnieper River | Statement: [Dnipro, locatedOnRiver, Dnieper River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dnieper River
Context triple: [Dnipro, locatedOnRiver, Dnieper River]
  • 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. 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.
  • C. Dniester
    The Dniester is a major river in Eastern Europe that flows through Ukraine and Moldova before emptying into the Black Sea.
  • D. Kuban River
    The Kuban River is a major river in the North Caucasus region of Russia that flows through the Krasnodar Krai before emptying into the Sea of Azov.
  • E. Daugava River
    The Daugava River is a major Eastern European river flowing through Russia, Belarus, and Latvia before emptying 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_69a8862e61708190af97b9838cc3f5de completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa648d9f2c8190aca4884648a69eb0 completed March 6, 2026, 5:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae030371e88190982c822a460d3e47 completed March 8, 2026, 11:15 p.m.
Created at: March 4, 2026, 7:31 p.m.