Triple

T21354086
Position Surface form Disambiguated ID Type / Status
Subject Pina River E526565 entity
Predicate mouthLocation P417 FINISHED
Object Pripyat 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: Pripyat River | Statement: [Pina River, mouthLocation, Pripyat River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pripyat River
Context triple: [Pina River, mouthLocation, Pripyat River]
  • A. Pripyat River chosen
    The Pripyat River is a major Eastern European waterway flowing through Ukraine and Belarus, known for passing near the Chernobyl Exclusion Zone and feeding into the Dnieper River.
  • B. Cherna River
    The Cherna River is a watercourse in southern Bulgaria that flows through the Rhodope Mountains near the town of Smolyan.
  • C. Dubna River
    The Dubna River is a waterway in central Russia that serves as a tributary of the Volga River and gives its name to the nearby town of Dubna.
  • D. Bucha River
    The Bucha River is a small river in northern Ukraine that flows through Kyiv Oblast and the town of Bucha before joining the Irpin River.
  • E. Syniukha River
    The Syniukha River is a river in central Ukraine that serves as a significant right-bank tributary of the Southern Bug, flowing through the Kirovohrad and Mykolaiv regions.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8af9aa9508190b756cc8e07084c8e completed April 22, 2026, 11:23 a.m.
Created at: April 16, 2026, 5:05 p.m.