Triple
T13084632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essingeleden |
E310298
|
entity |
| Predicate | hasStructure |
P35
|
FINISHED |
| Object | Essingebron |
E1021085
|
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: Essingebron | Statement: [Essingeleden, hasStructure, Essingebron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Essingebron Context triple: [Essingeleden, hasStructure, Essingebron]
-
A.
Essingebron
chosen
Essingebron is a bridge in Stockholm, Sweden, that connects the island of Lilla Essingen with the surrounding road network.
-
B.
Garrelsweer
Garrelsweer is a small village in the province of Groningen in the Netherlands, situated within the municipality of Eemsdelta.
-
C.
Reimerswaal
Reimerswaal is a coastal municipality in the Dutch province of Zeeland, known for its agricultural landscape and location along the Eastern Scheldt estuary.
-
D.
Islandsbron
Islandsbron is a notable bridge in Uppsala, Sweden, spanning the Fyris River and connecting central parts of the city.
-
E.
Oosteinderpoel
Oosteinderpoel is a water area or sub-lake that forms part of the Westeinderplassen lake system 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e272629c8190926dbc9df447b6c4 |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 9:02 p.m.