Triple
T5535343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martinus Nijhoff Bridge |
E145147
|
entity |
| Predicate | crosses |
P416
|
FINISHED |
| Object | River Waal |
E328453
|
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: River Waal | Statement: [Martinus Nijhoff Bridge, crosses, River Waal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: River Waal Context triple: [Martinus Nijhoff Bridge, crosses, River Waal]
-
A.
River Waal
chosen
River Waal is a major distributary branch of the Rhine in the Netherlands, serving as an important waterway for transport and trade.
-
B.
river Vecht
The river Vecht is a Dutch waterway in the province of Utrecht, known for its scenic, historic towns and country estates along its banks.
-
C.
river Eem
The river Eem is a short Dutch river in the province of Utrecht that flows through towns such as Amersfoort and Baarn before emptying into the Eemmeer.
-
D.
Vaartsche Rijn
Vaartsche Rijn is a historic canal in the Dutch province of Utrecht that connects the city of Utrecht with the Lower Rhine and forms part of its inland waterway network.
-
E.
Gelderse IJssel
Gelderse IJssel is the Dutch name for the branch of the River IJssel that flows through the province of Gelderland in the Netherlands.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01faed1d08190b6a57faedaf1b56a |
completed | March 22, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04ce1bce4819095559af19cf072f8 |
completed | March 22, 2026, 8:11 p.m. |
Created at: March 22, 2026, 3:34 p.m.