Triple

T14930253
Position Surface form Disambiguated ID Type / Status
Subject Yorckstraße E372241 entity
Predicate connectedTo P37 FINISHED
Object Mehringdamm E74577 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: Mehringdamm | Statement: [Yorckstraße, connectedTo, Mehringdamm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mehringdamm
Context triple: [Yorckstraße, connectedTo, Mehringdamm]
  • A. Mehringdamm chosen
    Mehringdamm is a Berlin U-Bahn station in the Kreuzberg district that serves as an interchange between lines U6 and U7.
  • B. Hohenzollerndamm
    Hohenzollerndamm is a major thoroughfare in Berlin known for its residential buildings, offices, and role as an important traffic artery in the Wilmersdorf district.
  • C. Malchower Chaussee
    Malchower Chaussee is a main road in Berlin that serves as a key access route to the Malchow locality.
  • D. Tempelhofer Damm
    Tempelhofer Damm is a major thoroughfare in Berlin’s Tempelhof district, running alongside the former Tempelhof Airport and connecting central Berlin with the city’s southern suburbs.
  • E. Kurfürstendamm
    Kurfürstendamm is one of Berlin’s most famous boulevards, known for its upscale shops, restaurants, and vibrant urban life.
  • 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_69d85cc9da0c81908d583ca3f63a3908 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded64550dc8190ba44120df00ba498 completed April 15, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff4c2d21348190a8045cf1847396e0 completed May 9, 2026, 3:01 p.m.
Created at: April 10, 2026, 2:36 a.m.