Triple

T20788403
Position Surface form Disambiguated ID Type / Status
Subject Sellin Ost railway station E511701 entity
Predicate partOf P40 FINISHED
Object Rügen railway network NE NERFINISHED

How this triple was built (3 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ügen railway network | Statement: [Sellin Ost railway station, partOf, Rügen railway network]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rügen railway network
Context triple: [Sellin Ost railway station, partOf, Rügen railway network]
  • A. Stralsund–Sassnitz railway
    The Stralsund–Sassnitz railway is a key rail line in northeastern Germany that connects the mainland city of Stralsund with the Baltic Sea island of Rügen and its ferry port at Sassnitz.
  • B. Lübeck–Rostock rail corridor
    The Lübeck–Rostock rail corridor is a key railway line in northern Germany that connects the Hanseatic cities of Lübeck and Rostock along the Baltic coast.
  • C. Berlin–Stralsund railway
    The Berlin–Stralsund railway is a major rail line in northeastern Germany that connects the capital Berlin with the Baltic Sea port city of Stralsund, serving as an important route for both regional and long-distance traffic.
  • D. Berlin–Rostock railway
    The Berlin–Rostock railway is a major German rail line connecting the capital city Berlin with the Baltic Sea port of Rostock, serving as an important route for both passenger and freight traffic in northeastern Germany.
  • E. Neumünster–Flensburg railway
    The Neumünster–Flensburg railway is a mainline rail route in the German state of Schleswig-Holstein that connects the inland city of Neumünster with the northern border city of Flensburg, serving both regional and long-distance traffic.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Rügen railway network
Target entity description: The Rügen railway network is the system of rail lines and services that connects towns and tourist destinations across Germany’s Baltic Sea island of Rügen.
  • A. Stralsund–Sassnitz railway chosen
    The Stralsund–Sassnitz railway is a key rail line in northeastern Germany that connects the mainland city of Stralsund with the Baltic Sea island of Rügen and its ferry port at Sassnitz.
  • B. Lübeck–Rostock rail corridor
    The Lübeck–Rostock rail corridor is a key railway line in northern Germany that connects the Hanseatic cities of Lübeck and Rostock along the Baltic coast.
  • C. Berlin–Stralsund railway
    The Berlin–Stralsund railway is a major rail line in northeastern Germany that connects the capital Berlin with the Baltic Sea port city of Stralsund, serving as an important route for both regional and long-distance traffic.
  • D. Berlin–Rostock railway
    The Berlin–Rostock railway is a major German rail line connecting the capital city Berlin with the Baltic Sea port of Rostock, serving as an important route for both passenger and freight traffic in northeastern Germany.
  • E. Neumünster–Flensburg railway
    The Neumünster–Flensburg railway is a mainline rail route in the German state of Schleswig-Holstein that connects the inland city of Neumünster with the northern border city of Flensburg, serving both regional and long-distance traffic.
  • F. None of above.

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_69e0b4cb83948190bd57bec21d78ed53 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c28dfb8c8190a10289c157a61c67 completed April 21, 2026, 12:19 a.m.
Created at: April 16, 2026, 12:38 p.m.