Triple
T15968878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiddenhausen |
E387267
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Bünde |
E391098
|
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: Bünde | Statement: [Hiddenhausen, hasNeighbouringMunicipality, Bünde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bünde Context triple: [Hiddenhausen, hasNeighbouringMunicipality, Bünde]
-
A.
Bünde
chosen
Bünde is a small town in the German state of North Rhine-Westphalia, known historically for its cigar industry and location in the Herford district.
-
B.
Nordhorn
Nordhorn is a town in Lower Saxony, Germany, known as the administrative center of the Grafschaft Bentheim district near the Dutch border.
-
C.
Meppen
Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
-
D.
Werdohl
Werdohl is a town in the Märkischer Kreis district of North Rhine-Westphalia, Germany, known for its metalworking industry and location in the hilly Sauerland region.
-
E.
Bentheim
Bentheim is a historical county in Lower Saxony, Germany, known for its Reformed Protestant heritage and the former County of Bentheim.
- 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_69fff293c2248190993d5d74eaf626bc |
completed | May 10, 2026, 2:50 a.m. |
Created at: April 10, 2026, 4:54 a.m.