Triple

T4484164
Position Surface form Disambiguated ID Type / Status
Subject N57 E107194 entity
Predicate passesNear P416 FINISHED
Object Hellevoetsluis E182040 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: Hellevoetsluis | Statement: [N57, passesNear, Hellevoetsluis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hellevoetsluis
Context triple: [N57, passesNear, Hellevoetsluis]
  • A. Hellevoetsluis chosen
    Hellevoetsluis is a historic Dutch port town known for its maritime heritage and coastal location in the western Netherlands.
  • B. Zaandam
    Zaandam is a city in the North Holland province of the Netherlands, known for its historic windmills, traditional wooden houses, and proximity to Amsterdam.
  • C. Delfzijl
    Delfzijl is a port town in the northeast of the Netherlands, known for its maritime industry and location on the Ems estuary near the German border.
  • D. Katwijk
    Katwijk is a coastal town and municipality in the western Netherlands known for its North Sea beaches and historic fishing heritage.
  • E. Purmerend
    Purmerend is a Dutch city and municipality located in the province of North Holland, known historically as a market town north of Amsterdam.
  • 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_69bd43f84f788190a1383579c4a595be completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd52a54c6c8190a7421bea6e3c00f1 completed March 20, 2026, 1:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69d74fa545b8819092809c605542476a completed April 9, 2026, 7:05 a.m.
Created at: March 20, 2026, 12:58 p.m.