Triple
T13698609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Waal |
E328453
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object |
Brug bij Ewijk
Brug bij Ewijk is a major road bridge in the Netherlands that carries traffic across the River Waal near the town of Ewijk, forming part of an important national motorway route.
|
E1055996
|
NE FINISHED |
How this triple was built (4 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: Brug bij Ewijk | Statement: [River Waal, hasBridge, Brug bij Ewijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brug bij Ewijk Context triple: [River Waal, hasBridge, Brug bij Ewijk]
-
A.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
B.
Schoterbrug
Schoterbrug is a bridge spanning the Spaarne River in Haarlem, Netherlands, serving as an important local traffic connection.
-
C.
Wijk
Wijk is a short form of the Dutch given name Lodewijk, commonly used as an informal or familiar variant.
-
D.
Oosterwijtwerd
Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
-
E.
Ekeren
Ekeren is a northern district of the Belgian city of Antwerp, known for its residential character and green spaces.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Brug bij Ewijk Triple: [River Waal, hasBridge, Brug bij Ewijk]
Generated description
Brug bij Ewijk is a major road bridge in the Netherlands that carries traffic across the River Waal near the town of Ewijk, forming part of an important national motorway route.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Brug bij Ewijk Target entity description: Brug bij Ewijk is a major road bridge in the Netherlands that carries traffic across the River Waal near the town of Ewijk, forming part of an important national motorway route.
-
A.
Bullewijk
Bullewijk is a small waterway and urban canal in Amsterdam’s southeastern area, integrated into the city’s network of rivers and canals.
-
B.
Schoterbrug
Schoterbrug is a bridge spanning the Spaarne River in Haarlem, Netherlands, serving as an important local traffic connection.
-
C.
Wijk
Wijk is a short form of the Dutch given name Lodewijk, commonly used as an informal or familiar variant.
-
D.
Oosterwijtwerd
Oosterwijtwerd is a small village in the province of Groningen in the northern Netherlands, known for its rural character and historic church.
-
E.
Ekeren
Ekeren is a northern district of the Belgian city of Antwerp, known for its residential character and green spaces.
- F. None of above. chosen
Provenance (5 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_69f794559e9c81909ef8a6d9b9f480b3 |
completed | May 3, 2026, 6:30 p.m. |
| NEDg | Description generation | batch_69f798aab9c48190acaa78864e89411f |
completed | May 3, 2026, 6:49 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f79943e4f4819098fa82cb6a32e08a |
completed | May 3, 2026, 6:51 p.m. |
Created at: April 9, 2026, 9:54 p.m.