Triple
T14186111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vliet |
E351580
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Voorburg |
E379063
|
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: Voorburg | Statement: [Vliet, flowsThrough, Voorburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Voorburg Context triple: [Vliet, flowsThrough, Voorburg]
-
A.
Voorburg
chosen
Voorburg is a historic town in the Netherlands, now part of the municipality of Leidschendam-Voorburg, known for its rich cultural heritage and proximity to The Hague.
-
B.
Bleiswijk
Bleiswijk is a village in the Dutch province of South Holland, known for its greenhouse horticulture and location within the municipality of Lansingerland.
-
C.
Albrandswaard
Albrandswaard is a municipality in the western Netherlands, situated just south of Rotterdam in the province of South Holland.
-
D.
Onderdendam
Onderdendam is a small historic village in the Dutch province of Groningen, known for its canals, bridges, and traditional architecture.
-
E.
Egmond aan Zee
Egmond aan Zee is a coastal village in the Netherlands known for its sandy beaches, dunes, and historic lighthouse on the North Sea.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cd5778819092a03597bcdcc182 |
completed | April 14, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd19433dc08190b4d2f1aef1b2d67d |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 1:03 a.m.