Triple

T6945471
Position Surface form Disambiguated ID Type / Status
Subject Elbe–Havel Canal E160786 entity
Predicate nearCity P350 FINISHED
Object Genthin E155308 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: Genthin | Statement: [Elbe–Havel Canal, nearCity, Genthin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Genthin
Context triple: [Elbe–Havel Canal, nearCity, Genthin]
  • A. Genthin chosen
    Genthin is a small town in the German state of Saxony-Anhalt, historically part of Prussia and known for its location along the Elbe–Havel Canal.
  • B. Prenzlau
    Prenzlau is a historic town in northeastern Germany’s Brandenburg region, known for its medieval architecture and role as a regional administrative center.
  • C. Bischofswerda
    Bischofswerda is a small town in the Saxony region of eastern Germany, known as a local commercial and transport hub near the city of Dresden.
  • D. Zinnowitz
    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.
  • E. Hennigsdorf
    Hennigsdorf is a town in the German state of Brandenburg, located just northwest of Berlin and known for its industrial heritage and proximity to the Havel River.
  • 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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6da8a65c48190b6862fc60f6c7f7a completed March 27, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76185c1d08190938d9065eb323100 completed March 28, 2026, 5:05 a.m.
Created at: March 27, 2026, 2:28 p.m.