Triple
T15968897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Löhne |
E387268
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Werre River |
E180218
|
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: Werre River | Statement: [Löhne, locatedOn, Werre River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Werre River Context triple: [Löhne, locatedOn, Werre River]
-
A.
Idenburg River
The Idenburg River is a significant tributary in the river system of New Guinea, contributing to the flow and drainage basin of the Mamberamo River.
-
B.
Örtze River
The Örtze River is a river in Lower Saxony, Germany, known for flowing through the Lüneburg Heath before joining the Aller.
-
C.
Lorze River
The Lorze River is a Swiss river in the canton of Zug, known for flowing through the Ägeri Valley and the Höllgrotten caves before joining the Reuss.
-
D.
Werre
chosen
The Werre is a river in North Rhine-Westphalia, Germany, that flows through towns such as Detmold and Herford before joining the Weser.
-
E.
Wiese River
The Wiese River is a tributary of the Rhine flowing through parts of Germany and Switzerland, including the municipality of Riehen near Basel.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1572847f08190830e30125e829766 |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170db6c6881908f5670c8282f4097 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 4:54 a.m.