Triple

T15426262
Position Surface form Disambiguated ID Type / Status
Subject Biggekerke E369518 entity
Predicate nearbySettlement P350 FINISHED
Object Vlissingen E250539 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: Vlissingen | Statement: [Biggekerke, nearbySettlement, Vlissingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vlissingen
Context triple: [Biggekerke, nearbySettlement, Vlissingen]
  • A. Vlissingen chosen
    Vlissingen is a historic port city on the North Sea coast of the Dutch province of Zeeland, known for its maritime heritage and seaside promenade.
  • B. Hellevoetsluis
    Hellevoetsluis is a historic Dutch port town known for its maritime heritage and coastal location in the western Netherlands.
  • C. Terneuzen
    Terneuzen is a port city and municipality in the southwestern Netherlands, known for its location on the Western Scheldt and its role in shipping access to the port of Ghent.
  • D. 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.
  • E. Oostduinkerke
    Oostduinkerke is a coastal village in West Flanders, Belgium, known for its North Sea beaches and traditional shrimp fishing on horseback.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec1fb288190a3625b8e4f487dd1 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00580789c08190994c5c71525aadc6 completed May 10, 2026, 10:03 a.m.
Created at: April 10, 2026, 3:20 a.m.