Triple

T21312152
Position Surface form Disambiguated ID Type / Status
Subject Vorma E525365 entity
Predicate hasBridge P386 FINISHED
Object Minnesund Bridge 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: Minnesund Bridge | Statement: [Vorma, hasBridge, Minnesund Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minnesund Bridge
Context triple: [Vorma, hasBridge, Minnesund Bridge]
  • A. Minnesund Bridge chosen
    Minnesund Bridge is a road and railway bridge in Norway that spans the southern end of Lake Mjøsa, connecting the village of Minnesund to surrounding regions.
  • B. Stäket Bridge
    Stäket Bridge is a road bridge in Sweden that spans the narrow waterway at Stäket, connecting key routes northwest of Stockholm.
  • C. Alssund Bridge
    Alssund Bridge is a road bridge in Sønderborg, Denmark, that spans the Alssund strait and connects the island of Als with the Jutland mainland.
  • D. Ranfjord Bridge
    Ranfjord Bridge is a road bridge in Nordland county, Norway, that spans the Ranfjorden and connects communities on its northern and southern shores.
  • E. Vestsiden Bridge
    Vestsiden Bridge is a road bridge spanning the Porsgrunn River in Porsgrunn, Norway, connecting the town’s central areas across the waterway.
  • 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_69e0b518b8948190ad69cf9a8784d397 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e75dca66ac8190a5f0a372a9bc25a7 completed April 21, 2026, 11:21 a.m.
Created at: April 16, 2026, 4:22 p.m.