Triple
T6835325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leidsevaart |
E157434
|
entity |
| Predicate | runsThrough |
P416
|
FINISHED |
| Object | Hillegom |
E209080
|
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: Hillegom | Statement: [Leidsevaart, runsThrough, Hillegom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hillegom Context triple: [Leidsevaart, runsThrough, Hillegom]
-
A.
Hillegom
chosen
Hillegom is a town in the western Netherlands known for its flower bulb cultivation and location within the historic Duin- en Bollenstreek (Dune and Bulb Region).
-
B.
Hulst
Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
-
C.
Valkenswaard
Valkenswaard is a town in the southern Netherlands known for its strong equestrian culture and international show jumping events.
-
D.
Zaltbommel
Zaltbommel is a historic Dutch town in the province of Gelderland, known for its medieval center and strategic location along the River Waal.
-
E.
Hoeksche Waard
Hoeksche Waard is a rural island and municipality in South Holland, Netherlands, known for its agricultural landscape and small towns.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67a9ff88190b0d86331b3ea06aa |
completed | March 27, 2026, 7:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c934b54a7c81909cdccd01af24c73d |
completed | March 29, 2026, 2:18 p.m. |
Created at: March 27, 2026, 2:19 p.m.