Triple
T11406879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steenkerque |
E270260
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Steenkerke |
E639568
|
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: Steenkerke | Statement: [Steenkerque, historicalName, Steenkerke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Steenkerke Context triple: [Steenkerque, historicalName, Steenkerke]
-
A.
Koudekerke
Koudekerke is a village in the Dutch province of Zeeland, located near the North Sea coast on the former island of Walcheren.
-
B.
Oostduinkerke
chosen
Oostduinkerke is a coastal village in West Flanders, Belgium, known for its North Sea beaches and traditional shrimp fishing on horseback.
-
C.
Kerkrade
Kerkrade is a town in the southeastern Netherlands, near the German border, known for its mining history and the international music festival WMC Kerkrade.
-
D.
Bezuidenhout
Bezuidenhout is a neighborhood in The Hague, Netherlands, known for its residential character and proximity to major government and business districts.
-
E.
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.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014c820c81908538ba4a08e13230 |
completed | April 9, 2026, 7:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b834cee48190ac09c1e1df4c12d0 |
completed | April 20, 2026, 5:23 a.m. |
Created at: April 8, 2026, 9:34 p.m.