Triple
T31217002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netnod |
E795895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet exchange point operator |
C60777
|
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: Internet exchange point operator Context triple: [Netnod, instanceOf, Internet exchange point operator]
-
A.
interconnection services provider
An interconnection services provider is an entity that facilitates and manages the physical and logical connectivity between different networks, data centers, or service platforms to enable efficient, secure, and reliable data exchange.
-
B.
network operator
A network operator is an entity responsible for managing, maintaining, and ensuring the reliable, secure, and efficient operation of communication networks and related infrastructure.
-
C.
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.
-
D.
Internet infrastructure organization
chosen
An Internet infrastructure organization is an entity that designs, operates, or governs the foundational hardware, software, and protocols that enable global digital connectivity and data exchange.
-
E.
data center operator
A data center operator is responsible for monitoring, maintaining, and supporting the physical and logical infrastructure of data centers to ensure continuous, secure, and efficient operation of computing, storage, and networking systems.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.