Triple

T21456825
Position Surface form Disambiguated ID Type / Status
Subject Wolgast E529361 entity
Predicate connectedByRailTo P848 FINISHED
Object Züssow 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: Züssow | Statement: [Wolgast, connectedByRailTo, Züssow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Züssow
Context triple: [Wolgast, connectedByRailTo, Züssow]
  • A. Züssow chosen
    Züssow is a small railway junction village in northeastern Germany that serves as a key transfer point between regional trains and the Usedomer Bäderbahn line to the Baltic Sea island of Usedom.
  • B. Odershausen
    Odershausen is a village and district of the spa town Bad Wildungen in the state of Hesse, Germany.
  • C. Prenzlau
    Prenzlau is a rural locality and small town in Queensland, Australia, situated within the Somerset Region and known for its agricultural character.
  • D. Prenzlau
    Prenzlau is a historic town in northeastern Germany’s Brandenburg region, known for its medieval architecture and role as a regional administrative center.
  • E. Retzow
    Retzow is a small municipality in the Havelland district of the federal state of Brandenburg in northeastern Germany.
  • 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_69e0c458133481908ae8b41a12c4edec completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9d7af248190a3bc06a390f390bf completed April 23, 2026, 9:43 a.m.
Created at: April 16, 2026, 6:08 p.m.