Triple
T23306838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bečva River |
E590467
|
entity |
| Predicate | hasNameInCzech |
P17790
|
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: [Bečva River, hasNameInCzech, Bečva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bečva Context triple: [Bečva River, hasNameInCzech, 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.
Veliki Bečkerek
Veliki Bečkerek is the former name of the Serbian city now known as Zrenjanin, a regional center in the Banat area of Vojvodina.
-
D.
Dúbravka
Dúbravka is a borough of Bratislava known as a largely residential area with local amenities and green spaces on the city’s western side.
-
E.
Božava
Božava is a small coastal village and tourist resort on the island of Dugi Otok in Croatia, known for its picturesque harbor and nearby beaches.
- 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.