Triple
T14085005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datteln-Hamm Canal |
E338969
|
entity |
| Predicate | connectsMunicipality |
P4245
|
FINISHED |
| Object | Waltrop |
E990679
|
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: Waltrop | Statement: [Datteln-Hamm Canal, connectsMunicipality, Waltrop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waltrop Context triple: [Datteln-Hamm Canal, connectsMunicipality, Waltrop]
-
A.
Waltrop
chosen
Waltrop is a small town in western Germany’s North Rhine-Westphalia, known for its industrial heritage and location near the Ruhr area.
-
B.
Aldenhoven
Aldenhoven is a small municipality in western Germany’s North Rhine-Westphalia, situated near the city of Aachen.
-
C.
Bottendorf
Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
-
D.
Bocholt
Bocholt is a municipality in the Belgian province of Limburg, known for its rural character and local brewing tradition.
-
E.
Bocholt
Bocholt is a medium-sized German city in the state of North Rhine-Westphalia, known for its industrial heritage and proximity to the Dutch border.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5edff1b881909ea56dc2429ef2dd |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb676620481908ed2fa5687a21866 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:21 p.m.