Triple

T16242852
Position Surface form Disambiguated ID Type / Status
Subject Askøy E394295 entity
Predicate hasBridge P386 FINISHED
Object Askøy Bridge E1199792 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: Askøy Bridge | Statement: [Askøy, hasBridge, Askøy Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Askøy Bridge
Context triple: [Askøy, hasBridge, Askøy Bridge]
  • A. Askøy Bridge chosen
    Askøy Bridge is a long suspension bridge in western Norway that links the island municipality of Askøy to the city of Bergen across Byfjorden.
  • B. Spissøy Bridge
    Spissøy Bridge is a Norwegian road bridge that forms part of the Triangle Link connection between the island of Stord and the mainland.
  • C. Rennesøy Bridge
    Rennesøy Bridge is a road bridge in Rogaland county, Norway, that forms part of the regional network linking the island of Rennesøy to the mainland and surrounding islands.
  • D. Måløy Bridge
    Måløy Bridge is a long cantilever road bridge in Vestland county, Norway, connecting the town of Måløy on Vågsøy island to the mainland across the Ulvesund strait.
  • E. Beisfjord Bridge
    Beisfjord Bridge is a road bridge in Narvik, Norway, that spans the Beisfjorden and forms part of the key transport route in the region.
  • 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_69d87f2171208190951025e526947816 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e24560060c8190ace4f4c0bd0d886d completed April 17, 2026, 2:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a002d9de7548190974851dc54465f0b completed May 10, 2026, 7:02 a.m.
Created at: April 10, 2026, 5:04 a.m.