Triple
T8309486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mittelland Canal |
E194553
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Weser |
E33257
|
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: Weser | Statement: [Mittelland Canal, connects, Weser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weser Context triple: [Mittelland Canal, connects, Weser]
-
A.
Weser
chosen
The Weser is a major river in northwestern Germany that flows through several federal states before emptying into the North Sea.
-
B.
Rheine
Rheine is a German city in the state of North Rhine-Westphalia, known for its historical town center and location along the River Ems.
-
C.
Rhine
The Rhine is one of Europe's most important rivers, historically serving as a vital trade route and cultural boundary from the Alps through Germany to the North Sea.
-
D.
Elbe
The Elbe is one of Central Europe's major rivers, flowing from the Czech Republic through Germany to the North Sea and serving as an important waterway for transport, industry, and agriculture.
-
E.
Werra
The Werra is a major river in central Germany that forms one of the two headstreams of the Weser.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2d2c30819095075940479b75a7 |
completed | March 31, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd4c307881909996adedc959180f |
completed | April 3, 2026, 5:47 p.m. |
Created at: March 30, 2026, 5:54 p.m.