Triple

T8553897
Position Surface form Disambiguated ID Type / Status
Subject Haarlem–Leiden railway E202511 entity
Predicate serves P98 FINISHED
Object Hillegom E209080 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: Hillegom | Statement: [Haarlem–Leiden railway, serves, Hillegom]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hillegom
Context triple: [Haarlem–Leiden railway, serves, Hillegom]
  • A. Hillegom chosen
    Hillegom is a town in the western Netherlands known for its flower bulb cultivation and location within the historic Duin- en Bollenstreek (Dune and Bulb Region).
  • B. Hulst
    Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
  • C. Valkenswaard
    Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
  • D. Zwanenburg
    Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
  • E. Zaltbommel
    Zaltbommel is a historic Dutch town in the province of Gelderland, known for its medieval center and strategic location along the River Waal.
  • 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_69ca832610e08190b3b6c6cd2c250255 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe8894e7c8190bc0ae2ceec473ecb completed March 31, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69d02f4d26ec8190baacf68b7e6ca0eb completed April 3, 2026, 9:21 p.m.
Created at: March 30, 2026, 6:19 p.m.