Triple
T13255299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelkheim |
E315641
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Mühlhausen im Täle |
E984882
|
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: Mühlhausen im Täle | Statement: [Kelkheim, hasTwinTown, Mühlhausen im Täle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mühlhausen im Täle Context triple: [Kelkheim, hasTwinTown, Mühlhausen im Täle]
-
A.
Mühlhausen im Täle
chosen
Mühlhausen im Täle is a small municipality in the district of Göppingen in Baden-Württemberg, Germany, situated in the Fils Valley at the edge of the Swabian Jura.
-
B.
Bruckmühl
Bruckmühl is a market town in Upper Bavaria, Germany, known for its location along the Mangfall River and its proximity to the city of Rosenheim.
-
C.
Mühlingen
Mühlingen is a small municipality in the state of Baden-Württemberg in southern Germany.
-
D.
Mühlhausen
Mühlhausen is a historic town in central Germany, known for its well-preserved medieval architecture and cultural heritage.
-
E.
Obermühlhausen
Obermühlhausen is a small village in Bavaria, Germany, that forms part of the municipality of Dießen am Ammersee.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98f7517048190b4eac4e44e81ff66 |
completed | April 11, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a4240d881909f0ee898fd272826 |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:24 p.m.