Triple

T6248727
Position Surface form Disambiguated ID Type / Status
Subject Don River E139989 entity
Predicate tributary P415 FINISHED
Object Voronezh River E235301 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: Voronezh River | Statement: [Don River, tributary, Voronezh River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Voronezh River
Context triple: [Don River, tributary, Voronezh River]
  • A. Voronezh River chosen
    The Voronezh River is a major river in western Russia that flows through the city of Voronezh before joining the Don River.
  • B. 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.
  • C. Vyatka River
    The Vyatka River is a major river in western Russia that flows through the Kirov and Nizhny Novgorod regions and plays an important role in regional transport, ecology, and settlement.
  • D. Kazan River
    The Kazan River is a major river in the Republic of Tatarstan, Russia, flowing through the city of Kazan before emptying into the Volga River.
  • E. Byk River
    The Byk River is a tributary watercourse in Eastern Europe that flows through Moldova before joining the Dniester River.
  • 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_69c008b4858c819095b0199114a9a87b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0633a9a048190856d5247d3b28a2e completed March 22, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69c5191d2d248190b34edca246ee74b8 completed March 26, 2026, 11:31 a.m.
Created at: March 22, 2026, 4:24 p.m.