Triple
T7001152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERT Polska |
E162338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer emergency response team |
C9230
|
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: computer emergency response team Context triple: [CERT Polska, instanceOf, computer emergency response team]
-
A.
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.
-
B.
cybersecurity agency
chosen
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.
cybersecurity system
A cybersecurity system is an integrated set of tools, policies, and processes designed to protect digital assets, networks, and data from unauthorized access, attacks, and damage.
-
D.
counterterrorism task force
A counterterrorism task force is a specialized, multi-agency group organized to prevent, detect, and respond to terrorist threats and activities through intelligence gathering, operational coordination, and targeted interventions.
-
E.
information and communications technology organization
An information and communications technology organization is an entity that develops, manages, or delivers digital and networked technologies, services, and infrastructure to enable electronic communication, data processing, and information exchange.
- 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:33 p.m.