Triple
T32517703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaspersky Lab |
E831102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | antivirus vendor |
C60665
|
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: antivirus vendor Context triple: [Kaspersky Lab, instanceOf, antivirus vendor]
-
A.
Application security vendor
An application security vendor provides tools and services that identify, prevent, and remediate security vulnerabilities in software applications throughout their development and deployment lifecycle.
-
B.
endpoint protection software
Endpoint protection software is a security solution installed on devices such as laptops, desktops, and servers to detect, prevent, and respond to malware, exploits, and other threats targeting those endpoints.
-
C.
enterprise software vendor
An enterprise software vendor is a company that develops, sells, and supports large-scale software solutions designed to meet the complex, mission-critical needs of organizations.
-
D.
cybersecurity distributor
A cybersecurity distributor is a company that sources, aggregates, and resells cybersecurity products and services from multiple vendors to channel partners such as resellers, integrators, and managed service providers, often adding technical, logistical, and marketing support.
-
E.
network security company
A network security company is an organization that designs, implements, and manages technologies and services to protect computer networks, data, and systems from unauthorized access, attacks, and other cyber threats.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.