Triple

T18151240
Position Surface form Disambiguated ID Type / Status
Subject Königsplatz, Berlin E434505 entity
Predicate near P350 FINISHED
Object Brandenburg Gate 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: Brandenburg Gate | Statement: [Königsplatz, Berlin, near, Brandenburg Gate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brandenburg Gate
Context triple: [Königsplatz, Berlin, near, Brandenburg Gate]
  • A. Brandenburg Gate chosen
    The Brandenburg Gate is an iconic 18th-century monument in Berlin and one of Germany’s most recognizable symbols of history and national unity.
  • B. Brandenburg Gate (Potsdam)
    The Brandenburg Gate in Potsdam is a historic triumphal arch built in the 18th century that serves as one of the city's most prominent architectural landmarks.
  • C. 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.
  • D. Sandauer Tor
    Sandauer Tor is a historic city gate in Landsberg am Lech, Germany, forming part of the town’s preserved medieval fortifications.
  • E. Jannowitzbrücke
    Jannowitzbrücke is a Berlin U-Bahn and S-Bahn station located near the River Spree in the city center, serving as a key transit point on several urban rail lines.
  • 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de38d4e08190bc4d430b70b7e288 completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.