Triple
T9224304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everbeek |
E221640
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Denderstreek |
E419077
|
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: Denderstreek | Statement: [Everbeek, locatedIn, Denderstreek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Denderstreek Context triple: [Everbeek, locatedIn, Denderstreek]
-
A.
Denderstreek
chosen
Denderstreek is a region in Belgium known for its towns and landscapes along the River Dender, featuring a mix of historic urban centers and rural scenery.
-
B.
Cromstrijen
Cromstrijen was a former municipality in the Dutch province of South Holland, comprising several villages on the island of Hoeksche Waard.
-
C.
Strandvliet
Strandvliet is a metro station in Amsterdam that serves passengers on the city's rapid transit network.
-
D.
Bollenstreek
Bollenstreek is a coastal region in the western Netherlands famous for its extensive flower bulb fields and springtime tulip displays.
-
E.
Zandkreek
Zandkreek is a tidal waterway and former estuary in the Dutch province of Zeeland, known for its role in regional water management and coastal protection.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9c71c4819089dcc3689f322529 |
completed | April 1, 2026, 8:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0b1ba860c8190b621b9fe88bc6ba2 |
completed | April 4, 2026, 6:37 a.m. |
Created at: March 30, 2026, 7:28 p.m.