Triple
T31947735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuzzball router |
E815696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet infrastructure component |
C2108
|
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 infrastructure component Context triple: [Fuzzball router, instanceOf, Internet infrastructure component]
-
A.
internet infrastructure component
chosen
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.
-
B.
telecommunications infrastructure component
A telecommunications infrastructure component is a physical or virtual element—such as cables, antennas, switches, or routers—that enables the transmission, routing, and management of voice, data, and multimedia communications across networks.
-
C.
Internet infrastructure organization
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.
-
D.
Department of Defense network component
A Department of Defense network component is any hardware, software, or configuration element that participates in, secures, manages, or enables communication within DoD information networks.
-
E.
digital infrastructure company
A digital infrastructure company designs, builds, and operates the foundational technology systems—such as data centers, networks, cloud platforms, and connectivity services—that enable digital applications and services to function reliably and at scale.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:07 a.m.