Triple
T19414466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern Old Town |
E485671
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Käfigturm |
—
|
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: Käfigturm | Statement: [Bern Old Town, hasPart, Käfigturm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Käfigturm Context triple: [Bern Old Town, hasPart, Käfigturm]
-
A.
Käfigturm
chosen
Käfigturm is a historic medieval tower and former city gate in Bern, Switzerland, now serving as a prominent landmark and cultural venue.
-
B.
Falterturm
Falterturm is a distinctive historic tower in the Bavarian town of Kitzingen, known for its leaning structure and role as a former watchtower.
-
C.
Schmalzturm
Schmalzturm is a historic medieval tower and notable architectural landmark in the Bavarian town of Weißenburg in Bayern, Germany.
-
D.
Schmalzturm
Schmalzturm is a historic medieval tower in the Bavarian town of Landsberg am Lech, notable as a landmark of its old town fortifications.
-
E.
Schimmelturm
Schimmelturm is a historic tower and prominent architectural landmark in the Bavarian town of Lauingen, Germany.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af834fc81908cb176076de10c1c |
completed | April 20, 2026, 1:32 p.m. |
Created at: April 10, 2026, 1:37 p.m.