Triple
T13698605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Waal |
E328453
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object | Waalbrug |
E104989
|
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: Waalbrug | Statement: [River Waal, hasBridge, Waalbrug]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Waalbrug Context triple: [River Waal, hasBridge, Waalbrug]
-
A.
Waalbrug
chosen
Waalbrug is a historic steel arch bridge over the River Waal in Nijmegen, the Netherlands, known for its distinctive design and key role in World War II.
-
B.
Geeuwenbrug
Geeuwenbrug is a small village in the Dutch province of Drenthe, situated within the municipality of Westerveld.
-
C.
Zeelandbrug
Zeelandbrug is a long cantilever bridge in the Dutch province of Zeeland that spans the Eastern Scheldt estuary, connecting the islands of Schouwen-Duiveland and Noord-Beveland.
-
D.
Schellingwouderbrug
Schellingwouderbrug is a bridge in Amsterdam, Netherlands, that spans the IJ and connects the city with the Schellingwoude area.
-
E.
Willemsbrug
Willemsbrug is a prominent red steel cable-stayed bridge in Rotterdam, Netherlands, spanning the Nieuwe Maas and connecting the city’s northern and southern banks.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d4f35888190b2c3df62bde1ce6e |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.