Triple

T8862079
Position Surface form Disambiguated ID Type / Status
Subject North Moravia E210913 entity
Predicate hasRiver P165 FINISHED
Object Bečva E456734 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 | Statement: [North Moravia, hasRiver, Bečva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bečva
Context triple: [North Moravia, hasRiver, Bečva]
  • A. Bečva chosen
    Bečva is a river in the eastern Czech Republic that flows through the Moravian region before joining the Morava River.
  • B. Blšanka
    Blšanka is a small river in the Czech Republic that flows through the Ústí nad Labem and Karlovy Vary regions before joining the Ohře River.
  • C. Běloves
    Běloves is a district or locality within the town of Náchod in the Hradec Králové Region of the Czech Republic.
  • D. Bregava
    Bregava is a river in Bosnia and Herzegovina known for flowing through the town of Stolac before joining the Neretva River.
  • E. Pálava
    Pálava is a renowned wine-producing region in the Czech Republic, noted for its limestone hills and high-quality white wines, especially aromatic varieties.
  • 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_69ca838bbddc8190ab546d737e5d350f completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc610263048190931bb2c3ac573a08 completed April 1, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfa0c248108190815d593f44029183 completed April 3, 2026, 11:13 a.m.
Created at: March 30, 2026, 6:50 p.m.