Triple

T17430023
Position Surface form Disambiguated ID Type / Status
Subject Siege of Stralsund E423844 entity
Predicate location P40 FINISHED
Object Stralsund 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: Stralsund | Statement: [Siege of Stralsund, location, Stralsund]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stralsund
Context triple: [Siege of Stralsund, location, 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. 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.
  • C. 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.
  • D. Flensburg
    Flensburg is a historic port city in northern Germany near the Danish border, known for its maritime heritage and role as a regional administrative and cultural center in Schleswig-Holstein.
  • E. 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.
  • 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e448ffb9c8819099fabfeebdc06883 completed April 19, 2026, 3:16 a.m.
Created at: April 10, 2026, 5:46 a.m.