Triple
T14128212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olbernhau |
E340088
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Flöha River |
E985909
|
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: Flöha River | Statement: [Olbernhau, locatedOn, Flöha River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flöha River Context triple: [Olbernhau, locatedOn, Flöha River]
-
A.
Flöha River
chosen
The Flöha River is a tributary of the Zschopau River in Saxony, Germany, flowing through the Ore Mountains region and the town of Flöha.
-
B.
Fuhse River
The Fuhse River is a tributary waterway in northern Germany that flows through Lower Saxony before joining the Aller River.
-
C.
Arpath River
Arpath River is a mountain river in the Anantnag district of Jammu and Kashmir, India, known for its cold, clear waters fed by Himalayan glaciers and springs.
-
D.
Böhme River
The Böhme River is a small river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath region before joining the Aller.
-
E.
Regalica River
The Regalica River is a distributary of the Oder River in northwestern Poland that flows through the city of Szczecin and forms part of its important inland waterway system.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6098013c8190b1bac9d3fff60acd |
completed | April 14, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c2a938081909ccd9fe7c5021dc6 |
completed | May 9, 2026, 3 p.m. |
Created at: April 9, 2026, 10:22 p.m.