Triple
T23338648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wangen an der Aare |
E591672
|
entity |
| Predicate | hasNeighboringMunicipality |
P224
|
FINISHED |
| Object | Heimenhausen |
—
|
NE NERFINISHED |
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: Heimenhausen | Statement: [Wangen an der Aare, hasNeighboringMunicipality, Heimenhausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heimenhausen Context triple: [Wangen an der Aare, hasNeighboringMunicipality, Heimenhausen]
-
A.
Heimenhausen
chosen
Heimenhausen is a small municipality in the Oberaargau region of the canton of Bern in Switzerland.
-
B.
Haimhausen
Haimhausen is a small municipality in Upper Bavaria, Germany, known for its historic castle and rural setting north of Munich.
-
C.
Emmenhausen
Emmenhausen is a small village that forms part of the municipality of Bovenden in Lower Saxony, Germany.
-
D.
Helmarshausen
Helmarshausen is a historic district of the spa town Bad Karlshafen in northern Hesse, Germany, known for its medieval heritage and former Benedictine monastery.
-
E.
Mimmenhausen
Mimmenhausen is a village in the Bodenseekreis district of Baden-Württemberg, Germany, now incorporated into the municipality of Salem.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983099188190a2e05cf81d62a641 |
completed | April 29, 2026, 5:33 a.m. |
Created at: April 17, 2026, 5:17 p.m.