Triple

T16410507
Position Surface form Disambiguated ID Type / Status
Subject Morava River E398549 entity
Predicate majorTributary P415 FINISHED
Object Bečva River E590467 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: Bečva River | Statement: [Morava River, majorTributary, Bečva River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bečva River
Context triple: [Morava River, majorTributary, Bečva River]
  • A. Bečva River chosen
    The Bečva River is a significant river in the eastern Czech Republic, flowing through Moravia and contributing to the region’s hydrology and local settlements.
  • B. Žitava River
    The Žitava River is a river in southern Slovakia that flows through the Danubian Lowland before joining the Nitra River.
  • C. Bednja River
    The Bednja River is a river in northern Croatia that flows through towns such as Ludbreg before joining the Drava River.
  • D. Kamenice River
    The Kamenice River is a river in the northern Czech Republic that flows through the Bohemian Switzerland region before joining the Jizera River.
  • E. Ploučnice River
    The Ploučnice River is a river in the Liberec and Ústí nad Labem regions of the Czech Republic, known for its meandering course through sandstone landscapes and historic towns.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328731a408190b38dcab0b7bb65ff completed April 18, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00a50665d081908c07fe3cb59088b3 completed May 10, 2026, 3:32 p.m.
Created at: April 10, 2026, 5:09 a.m.