Triple

T1404988
Position Surface form Disambiguated ID Type / Status
Subject Provider Bridging E31670 entity
Predicate relatedTo P37 FINISHED
Object Provider Backbone Bridges E31670 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: Provider Backbone Bridges | Statement: [Provider Bridging, relatedTo, Provider Backbone Bridges]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Provider Backbone Bridges
Context triple: [Provider Bridging, relatedTo, Provider Backbone Bridges]
  • A. Provider Bridging chosen
    Provider Bridging is an IEEE 802.1 network technology that extends Ethernet to support scalable, VLAN-based traffic separation and forwarding across large carrier or provider networks.
  • B. Platform 6
    Platform 6 is one of the passenger train platforms at Cambridge railway station in Cambridge, England.
  • C. Fieldlink
    Fieldlink was an early digital payments and security startup co-founded by Max Levchin that later evolved into the company behind PayPal.
  • D. Service Broker
    Service Broker is a SQL Server feature that provides native support for reliable, asynchronous messaging and queuing within database applications.
  • E. Bee Network
    Bee Network is Greater Manchester’s integrated public transport system brand, unifying buses, trams, cycling and walking under a single, coordinated network.
  • 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_69a49918e1f88190ba610f9dc8114578 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c3bb3a9c81909db2ad91defd87b6 completed March 1, 2026, 10:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69ace573b9288190ac91d8f6ea94fa20 completed March 8, 2026, 2:56 a.m.
Created at: March 1, 2026, 7:59 p.m.