X.509 certificates
E6784
X.509 certificates are digital documents that bind a public key to an entity’s identity using a trusted certificate authority, forming the basis of public key infrastructure for secure communications.
All labels observed (11)
| Label | Occurrences |
|---|---|
| X.509 certificates canonical | 24 |
| X.509 | 10 |
| ITU-T Recommendation X.509 | 2 |
| Public Key Infrastructure | 1 |
| TLS certificates | 1 |
| X.509 client certificates | 1 |
| X.509 public key certificates | 1 |
| X.509 standard | 1 |
| X.509 v1 | 1 |
| X.509 v2 | 1 |
| X.509 v3 | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T63828 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: X.509 certificates Context triple: [TLS, usesMechanism, X.509 certificates]
-
A.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
B.
RSA
RSA is a widely used public-key cryptographic algorithm that enables secure key exchange and digital signatures in many internet security protocols.
-
C.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
D.
Diffie–Hellman key exchange
Diffie–Hellman key exchange is a foundational cryptographic protocol that enables two parties to securely establish a shared secret over an insecure communication channel.
-
E.
Wi‑Fi Protected Access
Wi‑Fi Protected Access is a family of security protocols designed to protect wireless computer networks by providing stronger data encryption and user authentication than earlier Wi‑Fi standards.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: X.509 certificates Target entity description: X.509 certificates are digital documents that bind a public key to an entity’s identity using a trusted certificate authority, forming the basis of public key infrastructure for secure communications.
-
A.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
B.
RSA
RSA is a widely used public-key cryptographic algorithm that enables secure key exchange and digital signatures in many internet security protocols.
-
C.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
D.
Diffie–Hellman key exchange
Diffie–Hellman key exchange is a foundational cryptographic protocol that enables two parties to securely establish a shared secret over an insecure communication channel.
-
E.
Wi‑Fi Protected Access
Wi‑Fi Protected Access is a family of security protocols designed to protect wireless computer networks by providing stronger data encryption and user authentication than earlier Wi‑Fi standards.
- F. None of above. chosen
Statements (64)
| Predicate | Object |
|---|---|
| instanceOf |
digital certificate
ⓘ
public key infrastructure component ⓘ |
| canContainExtension |
CRL distribution points
ⓘ
authority information access ⓘ authority key identifier ⓘ basic constraints ⓘ certificate policies ⓘ extended key usage ⓘ key usage ⓘ subject alternative name ⓘ subject key identifier ⓘ |
| definedBy |
X.509 certificates
self-linksurface differs
ⓘ
surface form:
ITU-T Recommendation X.509
|
| encodedAs | ASN.1 ⓘ |
| hasComponent |
extensions
ⓘ
issuer distinguished name ⓘ serial number ⓘ signature algorithm identifier ⓘ signature value ⓘ subject distinguished name ⓘ subject public key info ⓘ validity period ⓘ version ⓘ |
| hasField |
issuer
ⓘ
notAfter ⓘ notBefore ⓘ public key ⓘ signature ⓘ subject ⓘ |
| hasVersion |
X.509 certificates
self-linksurface differs
ⓘ
surface form:
X.509 v1
X.509 certificates self-linksurface differs ⓘ
surface form:
X.509 v2
X.509 certificates self-linksurface differs ⓘ
surface form:
X.509 v3
|
| issuedBy | certificate authority ⓘ |
| reliesOn |
certificate authority trust model
ⓘ
intermediate certificate ⓘ root certificate ⓘ |
| requires | private key for corresponding public key ⓘ |
| serializedAs |
DER
ⓘ
PEM ⓘ |
| standardizedBy |
International Organization for Standardization
ⓘ
surface form:
ISO
ITU Telecommunication Standardization Sector ⓘ
surface form:
ITU-T
|
| supportsRevocationVia |
certificate revocation list
ⓘ
online certificate status protocol ⓘ |
| trustEstablishedBy |
root certificate store
ⓘ
trust anchor ⓘ |
| usedFor |
authentication
ⓘ
binding a public key to an identity ⓘ client authentication ⓘ code signing ⓘ confidentiality ⓘ document signing ⓘ email protection ⓘ integrity ⓘ non-repudiation ⓘ server authentication ⓘ |
| usedIn | public key infrastructure ⓘ |
| usedInProtocol |
HTTPS
ⓘ
IPsec ⓘ STARTTLS ⓘ
surface form:
LDAP over TLS
S/MIME ⓘ SSH (via certificate-based keys) ⓘ SSL ⓘ TLS ⓘ |
| verifiedBy |
certificate authority
ⓘ
relying party ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: X.509 certificates Description of subject: X.509 certificates are digital documents that bind a public key to an entity’s identity using a trusted certificate authority, forming the basis of public key infrastructure for secure communications.
Referenced by (44)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
X.509 certificate
this entity surface form:
ITU-T Recommendation X.509
subject surface form:
X.509 certificate
this entity surface form:
X.509 v1
subject surface form:
X.509 certificate
this entity surface form:
X.509 v2
subject surface form:
X.509 certificate
this entity surface form:
X.509 v3
this entity surface form:
X.509
this entity surface form:
ITU-T Recommendation X.509
subject surface form:
Apple Developer ID certificate
this entity surface form:
X.509 standard
this entity surface form:
X.509
this entity surface form:
X.509
this entity surface form:
X.509 public key certificates
this entity surface form:
TLS certificates
this entity surface form:
X.509
this entity surface form:
X.509
this entity surface form:
X.509 client certificates
this entity surface form:
X.509
this entity surface form:
X.509
this entity surface form:
X.509