Triple
T16582891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walcheren |
E402879
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Oostkapelle |
E366701
|
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: Oostkapelle | Statement: [Walcheren, contains, Oostkapelle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oostkapelle Context triple: [Walcheren, contains, Oostkapelle]
-
A.
Oostkapelle
chosen
Oostkapelle is a coastal village in the Dutch province of Zeeland, known for its beaches, dunes, and location on the former island of Walcheren.
-
B.
Zwevegem
Zwevegem is a municipality in the Belgian province of West Flanders, known for its mix of rural villages and industrial heritage.
-
C.
Koudekerke
Koudekerke is a village in the Dutch province of Zeeland, located near the North Sea coast on the former island of Walcheren.
-
D.
Meerbeke
Meerbeke is a village in East Flanders, Belgium, best known for having long served as the traditional finish town of the Tour of Flanders cycling race.
-
E.
Kanegem
Kanegem is a small village in West Flanders, Belgium, known for its historic church and rural character.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35999088c8190900497f18728bd0b |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007597905881909df7dc49961b6a02 |
completed | May 10, 2026, 12:09 p.m. |
Created at: April 10, 2026, 5:16 a.m.