Triple
T19637954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ter Heijde |
E471450
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Ter Heijde |
E351587
|
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: Ter Heijde | Statement: [Battle of Ter Heijde, namedAfter, Ter Heijde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ter Heijde Context triple: [Battle of Ter Heijde, namedAfter, Ter Heijde]
-
A.
Ter Heijde
chosen
Ter Heijde is a small coastal village in the Dutch province of South Holland, known for its North Sea beach and seaside character.
-
B.
Rijndijk
Rijndijk is a small settlement located within the municipality of Ubbergen in the Netherlands.
-
C.
Heijningen
Heijningen is a small village in the Dutch province of North Brabant, located in the municipality of Moerdijk.
-
D.
Woudwetering
Woudwetering is a Dutch waterway in South Holland that serves as an important local canal near the village of Woubrugge.
-
E.
Heijen
Heijen is a village in the Dutch province of Limburg, located in the southeastern Netherlands near the Meuse River.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64107f3fc8190ace6ae67287d280c |
completed | April 20, 2026, 3:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a077ee2ba00819082c50c6b163becf4 |
completed | May 15, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:44 p.m.