Triple
T16893238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rožnov Furrow |
E424227
|
entity |
| Predicate | drainedBy |
P165
|
FINISHED |
| Object | Bečva 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: Bečva River | Statement: [Rožnov Furrow, drainedBy, Bečva River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bečva River Context triple: [Rožnov Furrow, drainedBy, 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 (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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc6b97c8190b18aca477d6ef647 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:29 a.m.