Triple

T14405366
Position Surface form Disambiguated ID Type / Status
Subject U-Bahnhof Seestraße E357181 entity
Predicate isLocatedUnder P10157 FINISHED
Object Seestraße E72451 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: Seestraße | Statement: [U-Bahnhof Seestraße, isLocatedUnder, Seestraße]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seestraße
Context triple: [U-Bahnhof Seestraße, isLocatedUnder, Seestraße]
  • A. Seestraße chosen
    Seestraße is a Berlin U-Bahn station on the U6 line located in the Wedding district of the city.
  • B. Munsterdamm
    Munsterdamm is a street in Berlin, Germany, situated near the Insulaner hill in the city's southwestern area.
  • C. Langenstraße
    Langenstraße is a district or neighborhood within the town of Rüthen in North Rhine-Westphalia, Germany.
  • D. Voßstraße
    Voßstraße is a street in central Berlin, Germany, historically notable for hosting key government buildings of the German Empire and Nazi era near Potsdamer Platz and the government quarter.
  • E. Geislinger Steige
    Geislinger Steige is a steep and historically significant railway incline in Germany, renowned as an early engineering feat of the Fils Valley Railway through the Swabian Jura.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de908804048190a4fe58afc2e0a5b6 completed April 14, 2026, 7:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd94a254f881908d9494d4602064ae completed May 8, 2026, 7:45 a.m.
Created at: April 10, 2026, 1:17 a.m.