Triple
T23306826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bečva River |
E590467
|
entity |
| Predicate | confluenceNear |
P8203
|
FINISHED |
| Object | Přerov |
—
|
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: Přerov | Statement: [Bečva River, confluenceNear, Přerov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Přerov Context triple: [Bečva River, confluenceNear, Přerov]
-
A.
Přerov
chosen
Přerov is a city in the Olomouc Region of the Czech Republic, known as an important industrial and transport hub on the Bečva River.
-
B.
Vsetín
Vsetín is a town in the eastern Czech Republic known as an industrial and cultural center of the Moravian Wallachia region.
-
C.
Břeclav
Břeclav is a town in the South Moravian Region of the Czech Republic, known as a local transport hub and gateway to the Lednice–Valtice cultural landscape near the Austrian and Slovak borders.
-
D.
Bražec
Bražec is a small village and administrative part of the town of Náchod in the Hradec Králové Region of the Czech Republic.
-
E.
Říčany
Říčany is a town in the Czech Republic, located just southeast of Prague and known as a popular residential and commuter suburb with historical roots.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972846fc819092ca2b9590b2e177 |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:05 p.m.