Triple

T17308756
Position Surface form Disambiguated ID Type / Status
Subject Friedrichshain-Kreuzberg E420234 entity
Predicate containsLandmark P1098 FINISHED
Object Schlesisches Tor E616361 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: Schlesisches Tor | Statement: [Friedrichshain-Kreuzberg, containsLandmark, Schlesisches Tor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schlesisches Tor
Context triple: [Friedrichshain-Kreuzberg, containsLandmark, Schlesisches Tor]
  • A. Schlesisches Tor chosen
    Schlesisches Tor is a historic U-Bahn station and well-known urban landmark in Berlin’s Kreuzberg district, noted for its distinctive elevated railway architecture and vibrant surrounding nightlife.
  • B. Opatowska Gate
    Opatowska Gate is a historic medieval city gate in Sandomierz, Poland, known as one of the town’s most recognizable architectural symbols.
  • C. Sandauer Tor
    Sandauer Tor is a historic city gate in Landsberg am Lech, Germany, forming part of the town’s preserved medieval fortifications.
  • D. Rieder Tor
    Rieder Tor is a historic city gate in Donauwörth, Germany, and one of the town’s best-known architectural landmarks.
  • E. 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.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43900eca88190930af0e4ec4fc0f9 completed April 19, 2026, 2:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180e30934819087b7c838c8874aff completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:43 a.m.