Triple
T9020855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostend–Bruges International Airport |
E215716
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Ostend |
E128320
|
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: Ostend | Statement: [Ostend–Bruges International Airport, nearbyCity, Ostend]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ostend Context triple: [Ostend–Bruges International Airport, nearbyCity, Ostend]
-
A.
Ostend
chosen
Ostend is a Belgian coastal city on the North Sea known for its beaches, port, and seaside tourism.
-
B.
Ostend
Ostend is a small residential and commercial settlement on Waiheke Island in New Zealand’s Hauraki Gulf.
-
C.
Gravelines
Gravelines is a coastal commune in northern France known for its historic fortifications and strategic position along the English Channel.
-
D.
Bruges
Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
-
E.
Antwerp
Antwerp is a major Belgian port city on the River Scheldt, renowned as a global center for the diamond trade and its historic Flemish art and architecture.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a43add08190983b7ac88576fd7e |
completed | April 1, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d02fc332c881908847e70bee4695af |
completed | April 3, 2026, 9:23 p.m. |
Created at: March 30, 2026, 7:07 p.m.