Triple

T20972188
Position Surface form Disambiguated ID Type / Status
Subject Orlík Reservoir E516529 entity
Predicate inflow P415 FINISHED
Object Otava 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: Otava River | Statement: [Orlík Reservoir, inflow, Otava River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Otava River
Context triple: [Orlík Reservoir, inflow, Otava River]
  • A. Otava River chosen
    The Otava River is a significant river in the Czech Republic that flows through the Bohemian Forest and South Bohemian landscapes before joining the Vltava River.
  • B. Seinäjoki River
    Seinäjoki River is a watercourse in western Finland that flows through and gives its name to the city of Seinäjoki.
  • C. Nokianvirta River
    The Nokianvirta River is a waterway in southwestern Finland that flows through the town of Nokia and has historically influenced the region’s settlement and industry.
  • D. Selke River
    The Selke River is a scenic watercourse in the Harz region of Germany, known for flowing through picturesque valleys and historic towns that attract hikers and nature enthusiasts.
  • E. Tankajoki River
    Tankajoki River is a watercourse located in the Sodankylä region of Finnish Lapland, known for its natural Arctic landscapes and wilderness surroundings.
  • 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_69e0b4fee5ac8190875fa9ceba1a5e5e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fba161d88190b8905891f449004e completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:44 p.m.