Triple

T6712803
Position Surface form Disambiguated ID Type / Status
Subject Kreuzberg E153187 entity
Predicate hasLandmark P105 FINISHED
Object Kottbusser Tor E549136 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: Kottbusser Tor | Statement: [Kreuzberg, hasLandmark, Kottbusser Tor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kottbusser Tor
Context triple: [Kreuzberg, hasLandmark, Kottbusser Tor]
  • A. Kröpeliner Tor
    Kröpeliner Tor is a historic medieval city gate and prominent architectural landmark in the German city of Rostock.
  • B. Frankfurter Tor
    Frankfurter Tor is a prominent square and transport hub in Berlin’s Friedrichshain district, notable for its twin-towered Stalinist architecture and role as a gateway to the city’s historic Karl-Marx-Allee.
  • C. Kottbusser Tor station chosen
    Kottbusser Tor station is a major Berlin U-Bahn interchange in the Kreuzberg district, known for its elevated platforms and location at a busy urban crossroads.
  • D. Hallesches Tor
    Hallesches Tor is a major Berlin U-Bahn interchange station in the Kreuzberg district, serving as a key hub for multiple subway lines.
  • E. Oranienburger Tor
    Oranienburger Tor is an underground station on Berlin’s U-Bahn network located near the historic Oranienburger Tor area in the central district of Mitte.
  • 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_69c68809b4608190a2509ddb5ab87f05 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d121a92c8190a03f384a8aba84da completed March 27, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69c700948788819087f9b466be337286 completed March 27, 2026, 10:11 p.m.
Created at: March 27, 2026, 2:07 p.m.