Triple
T27589441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ONOS |
E699759
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SDN controller |
C29205
|
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: SDN controller Context triple: [ONOS, instanceOf, SDN controller]
-
A.
data center network
A data center network is a specialized, high-performance communication infrastructure that interconnects servers, storage systems, and networking devices within and between data centers to enable efficient, reliable data exchange and application delivery.
-
B.
virtual network switch
A virtual network switch is a software-based device that connects virtual machines and other virtual network components within a host or cloud environment, forwarding traffic between them based on network configuration and policies.
-
C.
network automation platform
chosen
A network automation platform is a centralized system that orchestrates, configures, monitors, and manages network devices and services through automated workflows, policies, and integrations to improve efficiency, consistency, and reliability.
-
D.
data center switch family
A data center switch family is a cohesive portfolio of high-performance network switches designed to provide scalable, low-latency, and highly available connectivity for servers, storage, and other infrastructure within modern data centers.
-
E.
Cisco ACI construct
A Cisco ACI construct is a logical building block (such as tenants, application profiles, EPGs, contracts, and bridge domains) used to define, segment, and manage policy-driven network behavior within a Cisco Application Centric Infrastructure fabric.
- F. None of above.
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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:05 p.m.