Triple
T22658556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISRG Root X2 |
E559297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public key infrastructure root |
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: public key infrastructure root Context triple: [ISRG Root X2, instanceOf, public key infrastructure root]
-
A.
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.
-
B.
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.
-
C.
DNS root name server
A DNS root name server is a critical server in the Domain Name System hierarchy that answers queries for the root zone and directs resolvers to the appropriate top-level domain name servers.
-
D.
root class
The root class is the topmost class in an inheritance hierarchy from which all other classes directly or indirectly derive, providing shared structure and behavior.
-
E.
cryptographic key
A cryptographic key is a piece of information, usually a string of bits, used by cryptographic algorithms to encrypt, decrypt, sign, or verify data securely.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:07 p.m.