Triple
T8787697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillegom |
E209080
|
entity |
| Predicate | locatedInBorough |
P300
|
FINISHED |
| Object | Bollenstreek |
E245550
|
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: Bollenstreek | Statement: [Hillegom, locatedInBorough, Bollenstreek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bollenstreek Context triple: [Hillegom, locatedInBorough, Bollenstreek]
-
A.
Bollenstreek
chosen
Bollenstreek is a coastal region in the western Netherlands famous for its extensive flower bulb fields and springtime tulip displays.
-
B.
Schipbeek
Schipbeek is a small river in the eastern Netherlands that flows through the provinces of Overijssel and Gelderland before joining the IJssel.
-
C.
Nissewaard
Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
-
D.
Geervliet
Geervliet is a small historic town in the western Netherlands, located in the province of South Holland.
-
E.
Betuwe
Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f89a84c819085d4cfe4e6dfbda8 |
completed | March 31, 2026, 11:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d04729c39c8190a88a28288653399b |
completed | April 3, 2026, 11:03 p.m. |
Created at: March 30, 2026, 6:43 p.m.