Triple

T17655248
Position Surface form Disambiguated ID Type / Status
Subject Blansko E429605 entity
Predicate locatedOnRiver P165 FINISHED
Object Svitava 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: Svitava River | Statement: [Blansko, locatedOnRiver, Svitava River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svitava River
Context triple: [Blansko, locatedOnRiver, Svitava River]
  • A. Svitava River chosen
    The Svitava River is a significant river in the eastern Czech Republic that flows through cities such as Brno before joining the Svratka River.
  • B. Svitávka River
    The Svitávka River is a small watercourse in the Liberec Region of the Czech Republic that flows through the town of Zákupy and its surrounding landscape.
  • C. Žitava River
    The Žitava River is a river in southern Slovakia that flows through the Danubian Lowland before joining the Nitra River.
  • D. Opava River
    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.
  • E. Turiec River
    The Turiec River is a significant river in north-central Slovakia that flows through the Turiec Basin before joining the Váh River.
  • 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46e3fc6e8819080098a3cd0183811 completed April 19, 2026, 5:55 a.m.
Created at: April 10, 2026, 6:06 a.m.