Triple
T16040617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERT Division |
E389083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybersecurity research organization |
C425
|
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 research organization Context triple: [CERT Division, instanceOf, cybersecurity research organization]
-
A.
cybersecurity coordination body
A cybersecurity coordination body is an organization that facilitates collaboration, information sharing, and joint response among stakeholders to prevent, detect, and mitigate cyber threats.
-
B.
cybersecurity agency
A cybersecurity agency is an organization that protects digital systems, networks, and data from cyber threats through monitoring, prevention, incident response, and security consulting.
-
C.
security research advocacy program
A security research advocacy program is an organized initiative that promotes, supports, and coordinates ethical security research and responsible vulnerability disclosure between researchers, organizations, and the broader community.
-
D.
research and development organization
chosen
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
-
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.
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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.