Triple

T6574531
Position Surface form Disambiguated ID Type / Status
Subject Elmshorn E155525 entity
Predicate locatedNear P294 FINISHED
Object Itzehoe E292980 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: Itzehoe | Statement: [Elmshorn, locatedNear, Itzehoe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Itzehoe
Context triple: [Elmshorn, locatedNear, Itzehoe]
  • A. Itzehoe chosen
    Itzehoe is a historic town in northern Germany known for its medieval origins and role as a regional center in the state of Schleswig-Holstein.
  • B. 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.
  • C. Bremerhaven
    Bremerhaven is a major German port city on the North Sea, known for its maritime industry, shipbuilding, and role as a key hub for trade and logistics.
  • D. Husum
    Husum is a small coastal town in northern Germany known for its North Sea harbor, maritime heritage, and role as a local cultural and commercial center.
  • 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_69c688151254819080387f87deab8fa7 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae7134708190a0355519d117ab9c completed March 27, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c70ae438b0819086449c169e5c7e49 completed March 27, 2026, 10:55 p.m.
Created at: March 27, 2026, 1:53 p.m.