Triple

T19166889
Position Surface form Disambiguated ID Type / Status
Subject Mangere Mountain E469207 entity
Predicate near P350 FINISHED
Object Mangere 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: Mangere Bridge | Statement: [Mangere Mountain, near, Mangere Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mangere Bridge
Context triple: [Mangere Mountain, near, Mangere Bridge]
  • A. Mangere Bridge chosen
    Mangere Bridge is a major road bridge in Auckland, New Zealand, carrying traffic across the Manukau Harbour between the suburbs of Onehunga and Māngere.
  • 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. Raikot Bridge
    Raikot Bridge is a key suspension bridge on the Karakoram Highway in Pakistan that serves as the main gateway for travelers heading toward Fairy Meadows and Nanga Parbat.
  • D. Hokksund Bridge
    Hokksund Bridge is a road bridge in Hokksund, Norway, that carries traffic across the Drammenselva river and serves as a key local transport link.
  • E. Minnesund Bridge
    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.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f16035b481908667a4415a1a63c9 completed April 20, 2026, 9:26 a.m.
Created at: April 10, 2026, 12:06 p.m.