Triple

T10603448
Position Surface form Disambiguated ID Type / Status
Subject Achterwasser E275809 entity
Predicate locatedNear P294 FINISHED
Object Zinnowitz E419096 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: Zinnowitz | Statement: [Achterwasser, locatedNear, Zinnowitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zinnowitz
Context triple: [Achterwasser, locatedNear, Zinnowitz]
  • A. Zinnowitz chosen
    Zinnowitz is a seaside resort town on Germany’s Baltic Sea coast, known for its sandy beaches, historic spa architecture, and tourism on the island of Usedom.
  • B. Premnitz
    Premnitz is a small town in the Havelland region of Brandenburg, Germany, situated on the Havel River and known historically for its chemical industry.
  • C. Geringswalde
    Geringswalde is a small town in the Free State of Saxony in eastern Germany, known for its rural character and location within the Central Saxon region.
  • D. Lankwitz
    Lankwitz is a residential locality in the southwestern part of Berlin, known for its quiet neighborhoods, green spaces, and mix of historic and modern architecture.
  • E. Dennewitz
    Dennewitz is a village in Brandenburg, Germany, historically notable as the site of a major 1813 battle during the Napoleonic Wars.
  • 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_69d6aaf948d88190806cc3a8c47a3fb2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d6ded6d698819084f96f46ea941461 completed April 8, 2026, 11:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4f31e3d5c8190a044eaf67ebc9f08 completed April 19, 2026, 3:22 p.m.
Created at: April 8, 2026, 7:32 p.m.