Triple

T13305533
Position Surface form Disambiguated ID Type / Status
Subject Heemstede-Aerdenhout railway station E316926 entity
Predicate serves P98 FINISHED
Object Aerdenhout 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: Aerdenhout | Statement: [Heemstede-Aerdenhout railway station, serves, Aerdenhout]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aerdenhout
Context triple: [Heemstede-Aerdenhout railway station, serves, Aerdenhout]
  • A. Aerdenhout chosen
    Aerdenhout is an affluent, leafy residential village in North Holland, Netherlands, known for its spacious villas and wooded surroundings.
  • B. Roosendaal
    Roosendaal is a city in the southern Netherlands known as a regional center for commerce and transport near the Belgian border.
  • C. Kortenhoef
    Kortenhoef is a village in the Dutch province of North Holland, known for its lakes, peatlands, and scenic natural surroundings.
  • D. Schoonhoven
    Schoonhoven is a historic Dutch town in South Holland, renowned for its silver craftsmanship and picturesque riverside setting.
  • E. Woerden
    Woerden is a historic Dutch city and municipality in the central Netherlands, known for its medieval fortifications and traditional cheese market.
  • 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d990a76adc8190ab9abcdb79a21ca8 completed April 11, 2026, 12:07 a.m.
Created at: April 9, 2026, 9:28 p.m.