Triple
T13467805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Beveland |
E311547
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Wissenkerke |
E356655
|
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: Wissenkerke | Statement: [North Beveland, containsSettlement, Wissenkerke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wissenkerke Context triple: [North Beveland, containsSettlement, Wissenkerke]
-
A.
Wissenkerke
chosen
Wissenkerke is a village in the Dutch province of Zeeland, located on the island and municipality of Noord-Beveland.
-
B.
Liedekerke
Liedekerke is a municipality in the Flemish Brabant province of Belgium, situated in the Dutch-speaking region of Flanders.
-
C.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
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.
Wielsbeke
Wielsbeke is a municipality in the Belgian province of West Flanders.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf101a1081909f2aba6da47baacc |
completed | April 12, 2026, 2:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd19259070819089bd3caf66e5af29 |
completed | May 7, 2026, 10:58 p.m. |
Created at: April 9, 2026, 9:42 p.m.