Triple
T22499080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISRG Root X1 |
E556220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | X.509 certificate |
C3158
|
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: X.509 certificate Context triple: [ISRG Root X1, instanceOf, X.509 certificate]
-
A.
digital certificate
chosen
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.
-
B.
public key infrastructure component
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.
-
C.
ASN.1 standard
The ASN.1 standard is a formal notation used to define, encode, transmit, and decode structured data in a platform- and language-independent way, commonly used in telecommunications and cryptographic protocols.
-
D.
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.
-
E.
public-key cryptography standard
A public-key cryptography standard is a formally defined specification that governs how asymmetric key pairs are generated, distributed, and used to securely encrypt, decrypt, sign, and verify digital data.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.