Triple
T15346149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoeksche Waard |
E366923
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Dordtsche Kil |
E1137035
|
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: Dordtsche Kil | Statement: [Hoeksche Waard, borderedBy, Dordtsche Kil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dordtsche Kil Context triple: [Hoeksche Waard, borderedBy, Dordtsche Kil]
-
A.
Dordtsche Kil
chosen
Dordtsche Kil is a tidal river and shipping channel in the western Netherlands that connects the Hollands Diep to the Oude Maas and forms part of an important inland waterway route.
-
B.
Dinteloord
Dinteloord is a village in the Dutch province of North Brabant, known for its agricultural surroundings and sugar beet processing industry.
-
C.
Harksheide
Harksheide was a former municipality in Schleswig-Holstein, Germany, that later became part of the city of Norderstedt.
-
D.
Zandbergen
Zandbergen is a village in East Flanders, Belgium, that forms part of the municipality of Geraardsbergen.
-
E.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01f931408190828d87567cecaceb |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.