Triple
T19259097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEC 62351 |
E481597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybersecurity standard |
C5533
|
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 standard Context triple: [IEC 62351, instanceOf, cybersecurity standard]
-
A.
information security standard
chosen
An information security standard is a formalized set of policies, procedures, and controls designed to protect information assets by defining consistent requirements for confidentiality, integrity, and availability.
-
B.
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.
-
C.
security practice
A security practice is a repeatable method, process, or behavior designed to protect systems, data, and users from threats and vulnerabilities.
-
D.
ISO/IEC standard
An ISO/IEC standard is a formally agreed-upon specification developed jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) that defines common requirements, guidelines, or characteristics for products, services, or systems to ensure quality, safety, interoperability, and consistency across international markets.
-
E.
ICT standard
An ICT standard is an agreed set of technical specifications and guidelines that ensure interoperability, compatibility, security, and quality for information and communication technology products and services.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:28 p.m.