Triple
T22499129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Root CA X3 |
E556221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | root certificate authority |
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: root certificate authority Context triple: [DST Root CA X3, instanceOf, root certificate authority]
-
A.
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.
-
B.
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.
-
C.
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.
-
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.
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.
- 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.