Triple
T5860460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nieuwpoort |
E130261
|
entity |
| Predicate | locatedEastOf |
P4240
|
FINISHED |
| Object | Koksijde |
E246975
|
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: Koksijde | Statement: [Nieuwpoort, locatedEastOf, Koksijde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koksijde Context triple: [Nieuwpoort, locatedEastOf, Koksijde]
-
A.
Koksijde
chosen
Koksijde is a coastal municipality in West Flanders, Belgium, known for its North Sea beaches and seaside tourism.
-
B.
Wassenaar
Wassenaar is an affluent coastal town in the western Netherlands known for its wooded estates, beaches, and role as a residential area for diplomats and expatriates.
-
C.
Ankum
Ankum is a municipality in Lower Saxony, Germany, situated within the Osnabrück district.
-
D.
Lonsee
Lonsee is a small municipality in the Alb-Donau district of Baden-Württemberg, Germany, situated on the Swabian Jura near the city of Ulm.
-
E.
Middelkerke
Middelkerke is a Belgian coastal municipality and seaside resort town on the North Sea, known for its beaches and tourism.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03588dd8c81909491350140ea340e |
completed | March 22, 2026, 6:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b10b55a88190b525405b1e20ea77 |
completed | March 23, 2026, 3:18 a.m. |
Created at: March 22, 2026, 3:56 p.m.