Triple
T18304287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onstwedde |
E438441
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Musselkanaal |
—
|
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: Musselkanaal | Statement: [Onstwedde, locatedNear, Musselkanaal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Musselkanaal Context triple: [Onstwedde, locatedNear, Musselkanaal]
-
A.
Musselkanaal
chosen
Musselkanaal is a village in the Dutch province of Groningen, known historically for its canal and peat industry.
-
B.
Hoendiep canal
The Hoendiep canal is a historic waterway in the Dutch province of Groningen that has long served as an important route for regional transport and trade.
-
C.
Peelkanal (Peelkanaal)
Peelkanal (Peelkanaal) is a canal in the southeastern Netherlands that was constructed for drainage and navigation along the former peat bog region known as the Peel.
-
D.
Oudehoofdkanaal
Oudehoofdkanaal is a historic canal in the Dutch city of Leeuwarden, known for its role in the city’s traditional waterways and urban landscape.
-
E.
Hartelkanaal
The Hartelkanaal is a Dutch shipping and drainage canal in the province of South Holland that connects the port and industrial areas near Rotterdam with the larger waterway network.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5018256508190b024980e3a4a3ae9 |
completed | April 19, 2026, 4:23 p.m. |
Created at: April 10, 2026, 10:35 a.m.