Triple
T3472563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walcheren |
E73296
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Aagtekerke |
E361427
|
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: Aagtekerke | Statement: [Walcheren, contains, Aagtekerke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aagtekerke Context triple: [Walcheren, contains, Aagtekerke]
-
A.
Wissenkerke
Wissenkerke is a village in the Dutch province of Zeeland, located on the island and municipality of Noord-Beveland.
-
B.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
C.
Oudenarde
Oudenarde (Oudenaarde) is a historic town in East Flanders, Belgium, known for its medieval architecture, tapestry production, and role in early modern European conflicts.
-
D.
Steenokkerzeel
Steenokkerzeel is a municipality in the Belgian province of Flemish Brabant, known for its proximity to Brussels and its location near major transport infrastructure.
-
E.
Koudekerke
chosen
Koudekerke is a village in the Dutch province of Zeeland, located near the North Sea coast on the former island of Walcheren.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3cc8488190b97c732e3f600a90 |
completed | March 8, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b402ca92ac819081fd3b3c49a13e0a |
completed | March 13, 2026, 12:27 p.m. |
Created at: March 8, 2026, 3:17 p.m.