Triple
T16256017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbe at Litoměřice |
E394629
|
entity |
| Predicate | hasConfluenceWith |
P2416
|
FINISHED |
| Object | Ohře |
E91943
|
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: Ohře | Statement: [Elbe at Litoměřice, hasConfluenceWith, Ohře]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ohře Context triple: [Elbe at Litoměřice, hasConfluenceWith, Ohře]
-
A.
Ohře
chosen
The Ohře is a river in Central Europe that flows through Germany and the Czech Republic before joining the Elbe.
-
B.
Podyjí
Podyjí is a protected national park area in the Czech Republic known for its deep Dyje River valley, diverse ecosystems, and well-preserved natural landscapes.
-
C.
Brod nad Tichou
Brod nad Tichou is a small municipality and village in the Plzeň Region of the Czech Republic.
-
D.
Oľka
Oľka is a river in eastern Slovakia that serves as one of the tributaries feeding into the Ondava River.
-
E.
Hromovka
Hromovka is a ski area and slope complex that forms part of the mountain resort town of Špindlerův Mlýn in the Krkonoše (Giant) Mountains of the Czech Republic.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459a48f081909c76b38741b8f04e |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00354ca28081908f993619a332cbf6 |
completed | May 10, 2026, 7:35 a.m. |
Created at: April 10, 2026, 5:04 a.m.