Triple
T20679631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riddarfjärden |
E508255
|
entity |
| Predicate | crossedBy |
P416
|
FINISHED |
| Object | Centralbron |
E378586
|
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: Centralbron | Statement: [Riddarfjärden, crossedBy, Centralbron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Centralbron Context triple: [Riddarfjärden, crossedBy, Centralbron]
-
A.
Centralbron
chosen
Centralbron is a major road and railway bridge in central Stockholm that carries traffic between the island of Södermalm and the city’s northern districts.
-
B.
Stallbron
Stallbron is a bridge in central Stockholm, Sweden, connecting the island of Helgeandsholmen—home to the Parliament House—with the surrounding city.
-
C.
Kungsängsbron
Kungsängsbron is a notable bridge in Uppsala, Sweden, spanning the Fyris River and serving as an important local traffic connection.
-
D.
Tranebergsbron
Tranebergsbron is a major bridge in Stockholm, Sweden, carrying road traffic between the districts of Kungsholmen and Bromma across Tranebergssundet.
-
E.
Västmannagatan
Västmannagatan is a street in central Stockholm, Sweden, located near Odenplan and served by entrances to the city’s metro 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea516b88190b3e90d03fa981a44 |
completed | April 21, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08cd6cb9f88190a3bdd3d353b78eb0 |
completed | May 16, 2026, 8:02 p.m. |
Created at: April 16, 2026, 11:44 a.m.