Triple

T34696095
Position Surface form Disambiguated ID Type / Status
Subject Causeway Bridge E891034 entity
Predicate reducedCongestionOn P32500 FINISHED
Object Simpson Bay 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: Simpson Bay Bridge | Statement: [Causeway Bridge, reducedCongestionOn, Simpson Bay Bridge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reducedCongestionOn
Context triple: [Causeway Bridge, reducedCongestionOn, Simpson Bay Bridge]
  • A. relievesTrafficFrom chosen
    Indicates that one entity reduces or alleviates traffic congestion that would otherwise occur on another entity.
  • B. facilitatesTrafficTowards
    Indicates that one entity enables, promotes, or directs the movement or flow of traffic toward another entity.
  • C. significantlyShortensRouteBetween
    Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
  • D. canReduceSpeedTo
    Indicates that an entity has the capability to lower its speed to a specified level or threshold.
  • E. reducedTravelTimeFrom
    Indicates that one entity has caused or experienced a decrease in the amount of time required to travel from a specified origin entity.
  • F. None of above.

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_69f349db7ab8819086808e833f472871 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7237f53488190a70af2cc56d0e5ca completed May 3, 2026, 10:29 a.m.
PD Predicate disambiguation batch_69f72157af108190880317a62e634bb0 completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 2:05 a.m.