Triple
T15553453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehringplatz |
E370808
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Hallisches Tor |
E72035
|
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: Hallisches Tor | Statement: [Mehringplatz, locatedNear, Hallisches Tor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hallisches Tor Context triple: [Mehringplatz, locatedNear, Hallisches Tor]
-
A.
Hallesches Tor
chosen
Hallesches Tor is a major Berlin U-Bahn interchange station in the Kreuzberg district, serving as a key hub for multiple subway lines.
-
B.
Rieder Tor
Rieder Tor is a historic city gate in Donauwörth, Germany, and one of the town’s best-known architectural landmarks.
-
C.
Schottentor
Schottentor is a historic former city gate area in Vienna that now serves as a major public transport hub and landmark at the edge of the Innere Stadt.
-
D.
Siegestor
The Siegestor is a 19th-century triumphal arch in Munich, Germany, dedicated to Bavarian military glory and located between the districts of Maxvorstadt and Schwabing.
-
E.
Schwabentor
Schwabentor is a historic medieval city gate in Freiburg im Breisgau, Germany, known as one of the city’s iconic architectural landmarks.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a96c0c88190808f68601a36b506 |
completed | April 16, 2026, 2:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff4c3e67c881909a9fa1e483a364be |
completed | May 9, 2026, 3:01 p.m. |
Created at: April 10, 2026, 4:09 a.m.