Triple

T22777431
Position Surface form Disambiguated ID Type / Status
Subject Ziegelgraben Bridge E563740 entity
Predicate partOf P40 FINISHED
Object Rügendamm 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: Rügendamm | Statement: [Ziegelgraben Bridge, partOf, Rügendamm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rügendamm
Context triple: [Ziegelgraben Bridge, partOf, Rügendamm]
  • A. Rügendamm chosen
    Rügendamm is a causeway and bridge complex in northern Germany that connects the island of Rügen to the mainland across the Strelasund.
  • B. Rinkerode
    Rinkerode is a village in North Rhine-Westphalia, Germany, known as a district of the town of Drensteinfurt in the Münster region.
  • C. Oderberg
    Oderberg is a small historic town in northeastern Germany near the Oder River, known for its scenic natural surroundings and proximity to the Polish border.
  • D. Munsterdamm
    Munsterdamm is a street in Berlin, Germany, situated near the Insulaner hill in the city's southwestern area.
  • E. Diepgen
    Diepgen is a German surname most notably associated with Eberhard Diepgen, a long-serving former Governing Mayor of Berlin.
  • 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_69e24554497c819080b996e071de27c2 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17b6260a8819080e57481281dfe40 completed April 29, 2026, 3:30 a.m.
Created at: April 17, 2026, 3:28 p.m.