Triple
T3115808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Ostend |
E65059
|
entity |
| Predicate | place |
P373
|
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: [Siege of Ostend, place, Ostend]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ostend Context triple: [Siege of Ostend, place, Ostend]
-
A.
Ostend
chosen
Ostend is a Belgian coastal city on the North Sea known for its beaches, port, and seaside tourism.
-
B.
Bruges
Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
-
C.
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.
-
D.
Port of Antwerp
The Port of Antwerp is one of Europe’s largest and busiest seaports, serving as a key international hub for maritime trade, logistics, and industry in Belgium.
-
E.
Port of Bruges
The Port of Bruges is a Belgian seaport historically serving the city of Bruges and the nearby coastal area, now integrated into a larger port complex through its merger with the Port of Antwerp.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e40bc48190b9b17c706a2450d5 |
completed | March 8, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2039d9d408190b01e45f0ced5ca3d |
completed | March 12, 2026, 12:06 a.m. |
Created at: March 8, 2026, 3:04 p.m.