Triple
T1614746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blauwbrug |
E34690
|
entity |
| Predicate | crosses |
P416
|
FINISHED |
| Object | Amstel River |
E4253
|
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: Amstel River | Statement: [Blauwbrug, crosses, Amstel River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amstel River Context triple: [Blauwbrug, crosses, Amstel River]
-
A.
Amstel River
chosen
The Amstel River is a historic waterway in the Netherlands that flows through and gives its name to the city of Amsterdam.
-
B.
Beneden Merwede
Beneden Merwede is a major distributary branch of the Rhine–Meuse river system in the western Netherlands, important for inland shipping and regional water management.
-
C.
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.
-
D.
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.
-
E.
Oude Maas
The Oude Maas is a major distributary river in the western Netherlands that forms part of the complex Rhine–Meuse–Scheldt delta system.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9098f384c81909ef836ee779466e2 |
completed | March 5, 2026, 4:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae719b71488190ad3de9f58d0d46a3 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:28 p.m.