Triple

T19466442
Position Surface form Disambiguated ID Type / Status
Subject Laage E487011 entity
Predicate locatedNear P294 FINISHED
Object city of Rostock 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: city of Rostock | Statement: [Laage, locatedNear, city of Rostock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Rostock
Context triple: [Laage, locatedNear, city of 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. Schwerin
    Schwerin is a historic city in northern Germany known for its picturesque lakeside setting and landmark Schwerin Castle.
  • E. Neubrandenburg
    Neubrandenburg is a historic city in northeastern Germany known for its well-preserved medieval brick Gothic architecture and distinctive city wall with multiple gate towers.
  • 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_69d8e8d86d608190bd199a98d0297f27 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e633e1dccc819096feb1a514b9eb86 completed April 20, 2026, 2:10 p.m.
Created at: April 10, 2026, 1:39 p.m.