Triple
T28618266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | issuing CA |
E724320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | certificate authority role |
C3159
|
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: certificate authority role Context triple: [issuing CA, instanceOf, certificate authority role]
-
A.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
-
B.
PKI leader
A PKI leader is a security professional who oversees the design, implementation, governance, and continuous improvement of an organization’s public key infrastructure to ensure trusted digital identities, secure communications, and regulatory compliance.
-
C.
public key infrastructure component
chosen
A public key infrastructure component is an element (such as a certificate authority, registration authority, or repository) that issues, manages, stores, and validates digital certificates and cryptographic keys to enable secure, trusted communications.
-
D.
digital certificate
A digital certificate is an electronic credential issued by a trusted authority that binds a public key to an entity’s identity, enabling secure and authenticated communication over networks.
-
E.
Authenticator Assurance Level
Authenticator Assurance Level is a measure of the strength and reliability of an authentication process, indicating the degree of confidence that the user’s claimed identity is accurate based on the types and combinations of authenticators used.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:32 a.m.