Triple
T12019416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brussels–Charleroi Canal |
E286108
|
entity |
| Predicate | hasLock |
P2431
|
FINISHED |
| Object | Ruisbroek lock |
E959542
|
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: Ruisbroek lock | Statement: [Brussels–Charleroi Canal, hasLock, Ruisbroek lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruisbroek lock Context triple: [Brussels–Charleroi Canal, hasLock, Ruisbroek lock]
-
A.
Lembeek lock
chosen
Lembeek lock is a canal lock in Lembeek, Belgium, that regulates water levels and navigation along the Brussels–Charleroi Canal.
-
B.
Maasbracht lock
Maasbracht lock is a major navigation lock complex in the Netherlands that regulates water levels and vessel traffic along the Juliana Canal near Maasbracht.
-
C.
Wijnegem locks
The Wijnegem locks are a major lock complex in Wijnegem, Belgium, that regulates water levels and ship traffic on the Albert Canal near Antwerp.
-
D.
Borgharen lock complex
The Borgharen lock complex is a major hydraulic structure near Maastricht in the Netherlands that regulates water levels and navigation between the Meuse River and the Juliana Canal.
-
E.
Weurt lock
Weurt lock is a major Dutch navigation lock complex near Nijmegen that regulates water levels and ship traffic between the Waal River and the Amsterdam–Rhine Canal.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903dabf2c819084dcaa05ae0a6018 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49d4156ec8190bfc6d1180ac41d06 |
completed | May 1, 2026, 12:32 p.m. |
Created at: April 8, 2026, 9:47 p.m.