Triple
T6952543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstel |
E160962
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object | Ceintuurbaanbrug |
E35553
|
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: Ceintuurbaanbrug | Statement: [Amstel, hasBridge, Ceintuurbaanbrug]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ceintuurbaanbrug Context triple: [Amstel, hasBridge, Ceintuurbaanbrug]
-
A.
Ceintuurbaanbrug
chosen
Ceintuurbaanbrug is a bridge in Amsterdam that carries the Ceintuurbaan across the Amstel River, connecting neighborhoods in the southern part of the city.
-
B.
Noordzeeweg bridge
The Noordzeeweg bridge is a road bridge spanning the Van Starkenborghkanaal in the Netherlands, carrying Noordzeeweg across the canal.
-
C.
Schellingwouderbrug
Schellingwouderbrug is a bridge in Amsterdam, Netherlands, that spans the IJ and connects the city with the Schellingwoude area.
-
D.
IJmeer bridge
The IJmeer bridge is a proposed infrastructure project intended to create a direct connection across the IJmeer lake, improving transport links between Amsterdam and surrounding areas.
-
E.
Kinkerbrug
Kinkerbrug is a bridge in Amsterdam that spans the Kostverlorenvaart canal, connecting parts of the city's Oud-West area.
- 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_69c68850419081909fb426b8f5a304c7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dab18d648190a2f238fce3e59365 |
completed | March 27, 2026, 7:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7882e3cfc81909ca7ecf507ac9adc |
completed | March 28, 2026, 7:50 a.m. |
Created at: March 27, 2026, 2:29 p.m.