Triple

T5956396
Position Surface form Disambiguated ID Type / Status
Subject Rügendamm E132525 entity
Predicate regionServed P82 FINISHED
Object City of Stralsund E181851 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: City of Stralsund | Statement: [Rügendamm, regionServed, City of Stralsund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Stralsund
Context triple: [Rügendamm, regionServed, City of Stralsund]
  • A. Stralsund chosen
    Stralsund is a historic Hanseatic port city on Germany’s Baltic Sea coast, known for its well-preserved medieval old town and brick Gothic architecture.
  • B. Güstrow
    Güstrow is a historic town in northern Germany known for its Renaissance castle, brick Gothic cathedral, and association with sculptor Ernst Barlach.
  • C. Lübeck
    Lübeck is a historic Hanseatic city in northern Germany renowned for its medieval architecture and long-standing role as a key trading hub on the Baltic Sea.
  • D. Wismar
    Wismar is a historic Hanseatic port city on Germany’s Baltic Sea coast, known for its well-preserved medieval architecture and UNESCO-listed old town.
  • E. Rostock
    Rostock is a historic Hanseatic city in northern Germany known for its significant seaport on the Baltic Sea and its long maritime and trading tradition.
  • 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_69c0086b05cc8190a8f36a96927a525c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c039c1de80819085c97a0aa2d37f32 completed March 22, 2026, 6:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11ccdec948190a0792c351a6867b7 completed March 23, 2026, 10:58 a.m.
Created at: March 22, 2026, 4:02 p.m.