Triple

T21785448
Position Surface form Disambiguated ID Type / Status
Subject Beek E537822 entity
Predicate hasRailwayStation P918 FINISHED
Object Beek-Elsloo railway station — NE NERFINISHED

How this triple was built (3 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: Beek-Elsloo railway station | Statement: [Beek, hasRailwayStation, Beek-Elsloo railway station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Beek-Elsloo railway station
Context triple: [Beek, hasRailwayStation, Beek-Elsloo railway station]
  • A. Bloemendaal railway station
    Bloemendaal railway station is a local train station in the town of Bloemendaal in the Netherlands, serving regional rail services and connecting the area to nearby cities.
  • B. Vierlingsbeek railway station
    Vierlingsbeek railway station is a local train stop in the village of Vierlingsbeek in the Netherlands, serving regional rail services on the Nijmegen–Venlo line.
  • C. Moosseedorf railway station
    Moosseedorf railway station is a local train stop in the municipality of Moosseedorf in the canton of Bern, Switzerland, providing regional rail connections near Lake Moossee.
  • D. Heeze railway station
    Heeze railway station is a local train station in the village of Heeze in North Brabant, Netherlands, serving regional rail services on the Eindhoven–Weert line.
  • E. Loppersum railway station
    Loppersum railway station is a local train station in the village of Loppersum in the Dutch province of Groningen, serving regional rail services in the northern Netherlands.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Beek-Elsloo railway station
Target entity description: Beek-Elsloo railway station is a regional train station in the Dutch province of Limburg serving the towns of Beek and Elsloo on the Maastricht–Sittard railway line.
  • A. Bloemendaal railway station
    Bloemendaal railway station is a local train station in the town of Bloemendaal in the Netherlands, serving regional rail services and connecting the area to nearby cities.
  • B. Vierlingsbeek railway station
    Vierlingsbeek railway station is a local train stop in the village of Vierlingsbeek in the Netherlands, serving regional rail services on the Nijmegen–Venlo line.
  • C. Moosseedorf railway station
    Moosseedorf railway station is a local train stop in the municipality of Moosseedorf in the canton of Bern, Switzerland, providing regional rail connections near Lake Moossee.
  • D. Heeze railway station
    Heeze railway station is a local train station in the village of Heeze in North Brabant, Netherlands, serving regional rail services on the Eindhoven–Weert line.
  • E. Loppersum railway station
    Loppersum railway station is a local train station in the village of Loppersum in the Dutch province of Groningen, serving regional rail services in the northern Netherlands.
  • F. None of above. chosen

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_69e0c47198f881908cb0d237266c10e9 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f04630f4f08190910b9e499a4249ca completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:52 p.m.