Triple
T11170843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfhalden |
E264268
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Walzenhausen |
E994126
|
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: Walzenhausen | Statement: [Wolfhalden, borderedBy, Walzenhausen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walzenhausen Context triple: [Wolfhalden, borderedBy, Walzenhausen]
-
A.
Walzenhausen
chosen
Walzenhausen is a Swiss village and municipality in the canton of Appenzell Ausserrhoden, known for its scenic location above Lake Constance and views over the Rhine Valley.
-
B.
Balzhausen
Balzhausen is a small municipality in the Bavarian region of Swabia in southern Germany.
-
C.
Waigolshausen
Waigolshausen is a small municipality in the Schweinfurt district of Bavaria, Germany, known for its rural character and location in the Franconian region.
-
D.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
-
E.
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.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f67c5a9dc881909b695f7e87dfcdf6 |
completed | May 2, 2026, 10:36 p.m. |
Created at: April 8, 2026, 9:29 p.m.