Triple
T12362255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | city center of Ulm |
E294769
|
entity |
| Predicate | hasLandmark |
P105
|
FINISHED |
| Object | Metzgerturm |
E977723
|
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: Metzgerturm | Statement: [city center of Ulm, hasLandmark, Metzgerturm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metzgerturm Context triple: [city center of Ulm, hasLandmark, Metzgerturm]
-
A.
Metzgerturm
chosen
Metzgerturm is a historic medieval tower in Ulm, Germany, known as one of the city’s iconic fortification landmarks.
-
B.
Pulverturm
Pulverturm is a historic defensive tower that forms part of the medieval Musegg Wall fortifications in Lucerne, Switzerland.
-
C.
Reichenbacher Turm
Reichenbacher Turm is a historic medieval defensive tower and city gate in Görlitz, Germany, notable for its well-preserved architecture and role in the town’s fortifications.
-
D.
Spremberger Turm
Spremberger Turm is a historic medieval city tower and prominent architectural landmark in the German city of Cottbus.
-
E.
Mehlsack tower
The Mehlsack tower is a prominent historic white tower in Ravensburg, Germany, serving as a symbol of the medieval city and a notable part of its fortifications.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f91a1908190a8a4fa9da3b47933 |
completed | April 10, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f634721e948190bb8e97ef677b9f59 |
completed | May 2, 2026, 5:29 p.m. |
Created at: April 8, 2026, 9:54 p.m.