Triple

T21329267
Position Surface form Disambiguated ID Type / Status
Subject Belfry of Nieuwpoort E525853 entity
Predicate location P40 FINISHED
Object Nieuwpoort 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: Nieuwpoort | Statement: [Belfry of Nieuwpoort, location, Nieuwpoort]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nieuwpoort
Context triple: [Belfry of Nieuwpoort, location, Nieuwpoort]
  • A. Nieuwpoort
    Nieuwpoort is a small historic city in the Dutch province of South Holland, known for its well-preserved fortifications and picturesque setting along the River Lek.
  • B. Nieuwpoort chosen
    Nieuwpoort is a coastal town in West Flanders, Belgium, known for its historic harbor and its strategic role in World War I.
  • C. Milport
    Milport is a fictional British parliamentary constituency featured in Patrick O’Brian’s Aubrey–Maturin historical naval novels.
  • D. Wilhelmshaven
    Wilhelmshaven is a coastal city in northwestern Germany known for its major naval base and port on the North Sea.
  • E. Terneuzen port
    Terneuzen port is a major Dutch seaport and industrial hub on the Western Scheldt, known for its role in maritime trade and access to the Ghent–Terneuzen Canal.
  • 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_69e0b51b90788190a4dd823d962626da completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7ab4f95fc819087eb32dca7da689a completed April 21, 2026, 4:52 p.m.
Created at: April 16, 2026, 4:42 p.m.