Triple

T21456824
Position Surface form Disambiguated ID Type / Status
Subject Wolgast E529361 entity
Predicate hasRailwayStation P918 FINISHED
Object Wolgast station 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: Wolgast station | Statement: [Wolgast, hasRailwayStation, Wolgast station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wolgast station
Context triple: [Wolgast, hasRailwayStation, Wolgast station]
  • A. Wolgast Hafen station chosen
    Wolgast Hafen station is a regional railway station in the town of Wolgast in Mecklenburg-Vorpommern, Germany, serving as a local transport hub near the Baltic Sea coast.
  • B. Cuxhaven station
    Cuxhaven station is the primary railway station serving the coastal town of Cuxhaven in Lower Saxony, Germany.
  • C. Halethorpe station
    Halethorpe station is a Maryland Area Regional Commuter (MARC) rail stop serving the Penn Line in the Baltimore–Washington metropolitan area.
  • D. Ahlbeck station
    Ahlbeck station is a railway stop on the island of Usedom in Germany, serving the seaside resort of Ahlbeck on the Usedomer Bäderbahn line.
  • E. Gernrode station
    Gernrode station is a railway terminus in Gernrode, Germany, known as an endpoint of the narrow-gauge Selke Valley Railway in the Harz region.
  • 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.