Triple
T1503751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duo Security |
E33853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybersecurity company |
C114
|
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: cybersecurity company Context triple: [Duo Security, instanceOf, cybersecurity company]
-
A.
computer services company
chosen
A computer services company is an organization that provides technical expertise, support, and solutions related to computer systems, software, networks, and IT infrastructure for individuals or other businesses.
-
B.
computer security specialist
A computer security specialist is a professional who protects computer systems, networks, and data from unauthorized access, attacks, and vulnerabilities by implementing, monitoring, and improving security measures.
-
C.
component of the Cybersecurity and Infrastructure Security Agency
A component of the Cybersecurity and Infrastructure Security Agency is an organizational unit or program within CISA that carries out specific cybersecurity, infrastructure protection, emergency communications, or risk management functions in support of the agency’s mission.
-
D.
security program
A security program is an organized set of policies, processes, technologies, and resources designed to protect an organization’s assets, information, and operations from threats and vulnerabilities.
-
E.
network security tool
A network security tool is a software or hardware solution that monitors, analyzes, and protects network traffic and resources from unauthorized access, misuse, and cyber threats.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:24 p.m.