Triple

T6860727
Position Surface form Disambiguated ID Type / Status
Subject Poltava E158268 entity
Predicate locatedOnRiver P165 FINISHED
Object Vorskla River E213951 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: Vorskla River | Statement: [Poltava, locatedOnRiver, Vorskla River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vorskla River
Context triple: [Poltava, locatedOnRiver, Vorskla River]
  • A. Vorskla River chosen
    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.
  • B. Kharkiv River
    The Kharkiv River is a waterway in northeastern Ukraine that flows through and lends its name to the city of Kharkiv before joining the Lopan River.
  • C. 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.
  • D. Trubizh River
    The Trubizh River is a tributary of the Dnieper in central Ukraine, flowing through the historic town of Pereiaslav and the surrounding Kyiv region.
  • E. Teteriv River
    The Teteriv River is a waterway in northern Ukraine that flows through the city of Zhytomyr before joining the Dnieper River basin.
  • 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_69c68830cdbc8190a8301c7a9d9f651a completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d88659c8819084916663219a8198 completed March 27, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c748bcb4048190b3860ffdd962d48c completed March 28, 2026, 3:19 a.m.
Created at: March 27, 2026, 2:21 p.m.