Triple

T21032599
Position Surface form Disambiguated ID Type / Status
Subject Hisingen E518099 entity
Predicate connectedBy P37 FINISHED
Object Götaälvbron NE NERFINISHED

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: Götaälvbron | Statement: [Hisingen, connectedBy, Götaälvbron]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Götaälvbron
Context triple: [Hisingen, connectedBy, Götaälvbron]
  • A. Götaälvbron chosen
    Götaälvbron is a major bascule bridge in Gothenburg, Sweden, that historically carried road and tram traffic across the Göta älv river and served as an important transport link in the city.
  • B. Nockebybron
    Nockebybron is a bridge in western Stockholm, Sweden, connecting the districts of Nockeby and Kärsön across Lake Mälaren.
  • C. Skanstullsbron
    Skanstullsbron is a major road and metro bridge in Stockholm that spans the Hammarby Canal, linking the island district of Södermalm with the southern mainland.
  • D. Hisingsbron
    Hisingsbron is a major vertical-lift bridge in Gothenburg, Sweden, connecting the mainland to the island of Hisingen across the Göta älv.
  • E. Ekelundsbron
    Ekelundsbron is a bridge in Stockholm, Sweden, that spans the Karlberg Canal and connects areas on its banks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b503275c8190afd9a163f997c709 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc83828c81909c1ec745c0313c9f completed April 21, 2026, 4:26 a.m.
Created at: April 16, 2026, 1:56 p.m.