Triple
T15131080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ovezande |
E361419
|
entity |
| Predicate | hasRoadConnectionTo |
P11435
|
FINISHED |
| Object | Heinkenszand |
E316588
|
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: Heinkenszand | Statement: [Ovezande, hasRoadConnectionTo, Heinkenszand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinkenszand Context triple: [Ovezande, hasRoadConnectionTo, Heinkenszand]
-
A.
Heinkenszand
chosen
Heinkenszand is a village in the Dutch province of Zeeland that serves as a local center within the South Beveland region.
-
B.
Hoogvliet
Hoogvliet is a borough in the southwest of Rotterdam in the Netherlands, known for its residential areas and industrial surroundings along the Oude Maas river.
-
C.
Monnickendam
Monnickendam is a historic fishing town in North Holland, Netherlands, known for its well-preserved old harbor and traditional Dutch architecture.
-
D.
Londerzeel
Londerzeel is a municipality in the Flemish Brabant province of Belgium, known for its residential character and proximity to both Brussels and Antwerp.
-
E.
Woudwetering
Woudwetering is a Dutch waterway in South Holland that serves as an important local canal near the village of Woubrugge.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff45406c8c8190beb87d4bb5c50355 |
completed | May 9, 2026, 2:31 p.m. |
Created at: April 10, 2026, 3:06 a.m.