Triple
T22136207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Bay |
E547034
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Ostend |
—
|
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: Ostend | Statement: [Rocky Bay, hasNearbySettlement, Ostend]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ostend Context triple: [Rocky Bay, hasNearbySettlement, Ostend]
-
A.
Ostend
Ostend is a Belgian coastal city on the North Sea known for its beaches, port, and seaside tourism.
-
B.
Ostend
chosen
Ostend is a small residential and commercial settlement on Waiheke Island in New Zealand’s Hauraki Gulf.
-
C.
Ostend
Ostend is a district of Frankfurt am Main in Germany, known for its mix of historic neighborhoods, modern developments, and the European Central Bank’s headquarters.
-
D.
Gravelines
Gravelines is a coastal commune in northern France known for its historic fortifications and strategic position along the English Channel.
-
E.
Bruges
Bruges is a historic Belgian city renowned for its well-preserved medieval architecture, picturesque canals, and rich artistic heritage.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bac764819099ba4896a161ef1c |
completed | April 28, 2026, 9:42 p.m. |
Created at: April 16, 2026, 8:32 p.m.