Triple
T17920739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valašské Meziříčí |
E448059
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Bečva |
—
|
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: Bečva | Statement: [Valašské Meziříčí, locatedOnRiver, Bečva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bečva Context triple: [Valašské Meziříčí, locatedOnRiver, 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.
Bešeňová
Bešeňová is a village in northern Slovakia known for its popular thermal spa and aquapark resort.
-
C.
Biely Potok
Biely Potok was a former Slovak settlement in the Orava region that was submerged and abandoned during the creation of the Orava Reservoir.
-
D.
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.
-
E.
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.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30a11748190be41361d108aee58 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 10:20 a.m.