Triple
T21319364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dijle |
E525569
|
entity |
| Predicate | flowsThrough |
P225
|
FINISHED |
| Object | Rotselaar |
—
|
NE NERFINISHED |
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: Rotselaar | Statement: [Dijle, flowsThrough, Rotselaar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rotselaar Context triple: [Dijle, flowsThrough, Rotselaar]
-
A.
Rotselaar
chosen
Rotselaar is a municipality in the Flemish Brabant province of Belgium, known for its residential character and proximity to the city of Leuven.
-
B.
Beersel
Beersel is a municipality in the Flemish Brabant province of Belgium, known for its historic Beersel Castle and traditional lambic and gueuze breweries.
-
C.
Uithoorn
Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
-
D.
Schelderode
Schelderode is a village in East Flanders, Belgium, that forms part of the municipality of Merelbeke near Ghent.
-
E.
Maasbracht
Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ecf12248190bb4172ad7416775e |
completed | April 21, 2026, 1:42 p.m. |
Created at: April 16, 2026, 4:38 p.m.