Triple
T25615083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equinix, Inc. |
E642134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital infrastructure company |
C50543
|
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: digital infrastructure company Context triple: [Equinix, Inc., instanceOf, digital infrastructure company]
-
A.
networking technology company
A networking technology company designs, develops, and delivers hardware, software, and services that enable reliable, secure, and high-performance data communication between devices, systems, and networks.
-
B.
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.
-
C.
networking hardware company
A networking hardware company designs, manufactures, and sells physical devices and infrastructure that enable data communication and connectivity across computer networks.
-
D.
infrastructure management company
An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
-
E.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 4:59 p.m.