Triple
T7932770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud Armor |
E184222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DDoS protection service |
C6083
|
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: DDoS protection service Context triple: [Cloud Armor, instanceOf, DDoS protection service]
-
A.
server hosting service
A server hosting service provides and manages remote computing resources, including hardware, networking, storage, and uptime, so clients can deploy and run applications, websites, or services without maintaining physical infrastructure.
-
B.
cloud service
chosen
A cloud service is an on-demand, internet-delivered computing resource—such as storage, processing power, or applications—managed by a provider and accessed remotely by users.
-
C.
anti-spam service
An anti-spam service is a system that automatically detects, filters, and blocks unwanted or malicious messages to protect users and maintain clean communication channels.
-
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.
mobile security service
A mobile security service is a system that protects mobile devices, applications, and data from threats through features like malware detection, secure communication, access control, and real-time monitoring.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:08 p.m.