Triple

T7843113
Position Surface form Disambiguated ID Type / Status
Subject Stralsund E181851 entity
Predicate connectedTo P37 FINISHED
Object Rügendamm E132525 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: Rügendamm | Statement: [Stralsund, connectedTo, Rügendamm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rügendamm
Context triple: [Stralsund, connectedTo, 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. 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.
  • C. Schiffbauerdamm
    Schiffbauerdamm is a historic street along the Spree River in central Berlin, known for its theaters, cultural venues, and proximity to major political and tourist landmarks.
  • D. Durbach
    Durbach is a wine-growing municipality in southwestern Germany, renowned for its vineyards and picturesque location in the Black Forest region.
  • E. Zinkensdamm
    Zinkensdamm is a residential and recreational area in Stockholm known for its sports grounds, park spaces, and location on the island district of Södermalm.
  • 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_69ca8285d6488190a95d4c02d7354b53 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb163b32688190b463a9cd8fa3c690 completed March 31, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69cb5aded4048190b18604963784352c completed March 31, 2026, 5:25 a.m.
Created at: March 30, 2026, 4:48 p.m.