Triple

T20317728
Position Surface form Disambiguated ID Type / Status
Subject Maassluis railway station E510421 entity
Predicate partOf P40 FINISHED
Object Hoekse Lijn 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: Hoekse Lijn | Statement: [Maassluis railway station, partOf, Hoekse Lijn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoekse Lijn
Context triple: [Maassluis railway station, partOf, Hoekse Lijn]
  • A. Hoekse Lijn chosen
    Hoekse Lijn is a railway line in the Netherlands that connects Rotterdam with the coastal town of Hoek van Holland.
  • B. De Lijn
    De Lijn is the Flemish public transport company in Belgium that operates most regional bus and tram services in Flanders.
  • C. Oude Lijn
    The Oude Lijn is the oldest railway line in the Netherlands, connecting key cities such as Amsterdam, Haarlem, Leiden, The Hague, and Rotterdam.
  • D. Spoornet
    Spoornet was South Africa’s former state-owned freight rail operator, responsible for much of the country’s heavy rail transport before being restructured and rebranded.
  • E. GVB Ferries
    GVB Ferries is the ferry service operating across Amsterdam’s waterways, providing frequent, short-distance crossings that connect key parts of the city as part of its public transport system.
  • 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67788ca3c8190a3496fd54a5870d6 completed April 20, 2026, 6:59 p.m.
Created at: April 16, 2026, 11:19 a.m.