Triple
T21326294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belfry of Veurne |
E525765
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Veurne |
—
|
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: Veurne | Statement: [Belfry of Veurne, locatedIn, Veurne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Veurne Context triple: [Belfry of Veurne, locatedIn, Veurne]
-
A.
Veurne
chosen
Veurne is a historic town in western Belgium known for its well-preserved medieval center and Flemish Renaissance architecture.
-
B.
Wervik
Wervik is a historic town and municipality in the Belgian province of West Flanders, situated along the river Lys near the French border.
-
C.
Zwevegem
Zwevegem is a municipality in the Belgian province of West Flanders, known for its mix of rural villages and industrial heritage.
-
D.
Zeewolde
Zeewolde is a Dutch municipality and village known for its modern planned layout and location on reclaimed land in the province of Flevoland.
-
E.
Gavere
Gavere is a municipality in the Belgian province of East Flanders, known for its rural character and several constituent villages.
- 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_69e7ab49aa48819083b3793657903216 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 16, 2026, 4:41 p.m.