Triple

T14019650
Position Surface form Disambiguated ID Type / Status
Subject Demmin E337293 entity
Predicate locatedEastOf P4240 FINISHED
Object Rostock E56817 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: Rostock | Statement: [Demmin, locatedEastOf, Rostock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rostock
Context triple: [Demmin, locatedEastOf, Rostock]
  • A. Rostock chosen
    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.
  • B. Ratzeburg
    Ratzeburg is a historic town in northern Germany known for its island old town and Romanesque cathedral, situated in the lake district of Schleswig-Holstein.
  • 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. 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.
  • E. 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.
  • 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_69d81c6543a48190bd5ba93d7419e797 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2f3c7cd88190b236382058581740 completed April 14, 2026, 12:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd4c20e45c8190968a5d88a2b3fe37 completed May 8, 2026, 2:36 a.m.
Created at: April 9, 2026, 10:19 p.m.