Triple
T17135188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrondissement of Ypres |
E415817
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Wervik |
E1040288
|
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: Wervik | Statement: [Arrondissement of Ypres, containsMunicipality, Wervik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wervik Context triple: [Arrondissement of Ypres, containsMunicipality, Wervik]
-
A.
Wervik
chosen
Wervik is a historic town and municipality in the Belgian province of West Flanders, situated along the river Lys near the French border.
-
B.
Veurne
Veurne is a historic town in western Belgium known for its well-preserved medieval center and Flemish Renaissance architecture.
-
C.
Blankenberge
Blankenberge is a Belgian coastal town on the North Sea known for its sandy beaches, seaside promenade, and tourism.
-
D.
De Panne
De Panne is a Belgian seaside resort town on the North Sea coast, known for its beaches, dunes, and as the westernmost point of Belgium.
-
E.
Lieshout
Lieshout is a village in the Dutch province of North Brabant, known for its rural character and the Bavaria brewery.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02dca8881908efd73741397a207 |
completed | April 18, 2026, 8:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014150d63081908a5614f85694e57a |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:36 a.m.