Triple

T9941835
Position Surface form Disambiguated ID Type / Status
Subject Opava E194100 entity
Predicate river P165 FINISHED
Object Opava River E783583 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: Opava River | Statement: [Opava, river, Opava River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opava River
Context triple: [Opava, river, Opava River]
  • A. Opava River chosen
    The Opava River is a significant watercourse in the Czech Republic that flows through the historical region of Silesia, including the city of Opava, before joining the Oder River.
  • B. Svitava River
    The Svitava River is a significant river in the eastern Czech Republic that flows through cities such as Brno before joining the Svratka River.
  • C. Orlice River
    The Orlice River is a significant river in the Czech Republic that flows through eastern Bohemia and joins the Elbe near the city of Hradec Králové.
  • D. Sázava River
    The Sázava River is a scenic tributary of the Vltava in the Czech Republic, known for its picturesque valleys, historic sites, and popularity for canoeing and recreation.
  • E. Váh River
    The Váh River is the longest river in Slovakia, flowing from the Tatra Mountains through much of the country before joining the Danube.
  • 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_69ca82e409348190a393777356b80a2a completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb610905c81909d669265c92021a5 completed April 2, 2026, 12:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69d299d479d481908dc8fe2acc307a64 completed April 5, 2026, 5:20 p.m.
Created at: March 30, 2026, 8:44 p.m.