Triple

T20788207
Position Surface form Disambiguated ID Type / Status
Subject Bay of Prora E511696 entity
Predicate near P350 FINISHED
Object Sassnitz 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: Sassnitz | Statement: [Bay of Prora, near, Sassnitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sassnitz
Context triple: [Bay of Prora, near, Sassnitz]
  • A. Sassnitz chosen
    Sassnitz is a port town on the Baltic Sea coast of Germany, located on the island of Rügen and known as a gateway to nearby national parks and chalk cliffs.
  • B. Ueckermünde
    Ueckermünde is a small historic port town in northeastern Germany on the Szczecin Lagoon, known for its maritime heritage and access to the Baltic Sea.
  • C. Stolpmünde
    Stolpmünde is the former German name for the Baltic Sea port town now known as Ustka in northern Poland.
  • D. Ostseebad
    Ostseebad is a German designation for a seaside resort town on the Baltic Sea, recognized for its coastal tourism and spa facilities.
  • E. Lüchow
    Lüchow is a small historic town in Lower Saxony, Germany, known as an administrative and cultural center of the rural Wendland area.
  • 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_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.