Triple

T19068398
Position Surface form Disambiguated ID Type / Status
Subject Bragernes Torg E466726 entity
Predicate near P350 FINISHED
Object Drammen Bridge E1357472 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: Drammen Bridge | Statement: [Bragernes Torg, near, Drammen Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drammen Bridge
Context triple: [Bragernes Torg, near, Drammen Bridge]
  • A. Drammen Bridge chosen
    Drammen Bridge is a major road bridge in Drammen, Norway, carrying traffic across the Drammenselva river and connecting key parts of the city.
  • B. Lysaker Bridge
    Lysaker Bridge is a key road and rail bridge in the Oslo area of Norway, carrying major traffic across the Lysaker River between Oslo and Bærum.
  • C. Stord Bridge
    Stord Bridge is a major suspension bridge in western Norway that connects the island of Stord to the mainland as part of an important regional transport route.
  • D. Helgeland Bridge
    Helgeland Bridge is a long cable-stayed road bridge in Nordland county, Norway, known for connecting the town of Sandnessjøen to the mainland across the Alstenfjorden.
  • E. Sandvika Bridge
    Sandvika Bridge is a notable road bridge in the town of Sandvika, Norway, serving as an important local crossing and traffic connection.
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e19b94d08190865b62d98f718bb0 completed April 20, 2026, 8:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a05dd8a33bc8190bf43a9abfdcb052a completed May 14, 2026, 2:34 p.m.
Created at: April 10, 2026, 12:03 p.m.