Triple

T8111200
Position Surface form Disambiguated ID Type / Status
Subject Friedrichshain E189356 entity
Predicate hasLandmark P105 FINISHED
Object Frankfurter Tor E569407 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: Frankfurter Tor | Statement: [Friedrichshain, hasLandmark, Frankfurter Tor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frankfurter Tor
Context triple: [Friedrichshain, hasLandmark, Frankfurter Tor]
  • A. Frankfurter Tor chosen
    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.
  • B. 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.
  • C. Spandauer Tor
    Spandauer Tor was a historic city gate of Berlin that marked the entrance to the city on the road leading toward Spandau.
  • D. Berliner Tor
    Berliner Tor is a historic city gate in Wesel, Germany, notable for its baroque architecture and role in the town’s former fortifications.
  • 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_69ca82b9d5848190a24672775d5c5011 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb432bcb648190b5ddbcc2a3dbc9b1 completed March 31, 2026, 3:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc942a9af881908b7ddc724755893e completed April 1, 2026, 3:42 a.m.
Created at: March 30, 2026, 5:32 p.m.