Triple

T10824758
Position Surface form Disambiguated ID Type / Status
Subject Scheveningseweg E255467 entity
Predicate connects P390 FINISHED
Object Scheveningen E71726 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: Scheveningen | Statement: [Scheveningseweg, connects, Scheveningen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scheveningen
Context triple: [Scheveningseweg, connects, Scheveningen]
  • A. Scheveningen chosen
    Scheveningen is a popular seaside resort district of The Hague in the Netherlands, known for its long sandy beach, pier, and promenade along the North Sea coast.
  • B. Katwijk
    Katwijk is a coastal town and municipality in the western Netherlands known for its North Sea beaches and historic fishing heritage.
  • C. Noordwijk
    Noordwijk is a coastal town in the western Netherlands known for its North Sea beaches, flower bulb fields, and the nearby European Space Agency’s ESTEC facility.
  • D. Bleiswijk
    Bleiswijk is a village in the Dutch province of South Holland, known for its greenhouse horticulture and location within the municipality of Lansingerland.
  • E. Hellevoetsluis
    Hellevoetsluis is a historic Dutch port town known for its maritime heritage and coastal location in the western Netherlands.
  • 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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d734d0389c819090a892693c4046ed completed April 9, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c0cf61108190a15ab76454fc0d75 completed May 3, 2026, 9:40 p.m.
Created at: April 8, 2026, 9:19 p.m.