Triple
T7663689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infrastructure Services for Open Access |
E173572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open infrastructure provider |
C22379
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: open infrastructure provider Context triple: [Infrastructure Services for Open Access, instanceOf, open infrastructure provider]
-
A.
public cloud provider
A public cloud provider is a third-party company that offers scalable, on-demand computing resources and services over the internet to multiple customers on a shared infrastructure.
-
B.
broadcast infrastructure provider
A broadcast infrastructure provider is an organization that designs, builds, operates, and maintains the technical networks and facilities required to transmit audio, video, and data content from broadcasters to end audiences across various distribution platforms.
-
C.
infraorder
An infraorder is a taxonomic rank below suborder and above superfamily used to group closely related organisms within an order based on shared evolutionary characteristics.
-
D.
content delivery network provider
A content delivery network provider is a service that distributes and caches digital content across geographically dispersed servers to deliver fast, reliable, and scalable access to users worldwide.
-
E.
internet infrastructure component
An internet infrastructure component is a foundational hardware or software element—such as routers, switches, servers, cables, or protocols—that enables the transmission, routing, and reliable delivery of data across interconnected networks.
- F. None of above. chosen
Provenance (1 batch)
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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:59 p.m.