Triple
T22499155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Root CA X3 |
E556221
|
entity |
| Predicate | isTrustAnchorFor |
P33863
|
FINISHED |
| Object | Let’s Encrypt Authority X1 (via cross-signing chain) |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Let’s Encrypt Authority X1 (via cross-signing chain) | Statement: [DST Root CA X3, isTrustAnchorFor, Let’s Encrypt Authority X1 (via cross-signing chain)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Let’s Encrypt Authority X1 (via cross-signing chain) Context triple: [DST Root CA X3, isTrustAnchorFor, Let’s Encrypt Authority X1 (via cross-signing chain)]
-
A.
Let’s Encrypt R3 intermediate
The Let’s Encrypt R3 intermediate is a widely deployed intermediate certificate authority used by Let’s Encrypt to issue trusted TLS/SSL certificates for securing internet communications.
-
B.
Let’s Encrypt R3
Let’s Encrypt R3 is a widely used intermediate certificate authority operated by Let’s Encrypt under the ISRG Root X1 trust anchor to issue free, automated TLS/SSL certificates for secure web connections.
-
C.
Let’s Encrypt
Let’s Encrypt is a free, automated, and open certificate authority that provides TLS/SSL certificates to enable secure HTTPS connections for websites worldwide.
-
D.
DST Root CA X3
DST Root CA X3 is a widely trusted root certificate authority operated by IdenTrust that historically provided the cross-signed trust anchor enabling broad browser compatibility for Let’s Encrypt certificates.
-
E.
ISRG Root X1
ISRG Root X1 is the primary root certificate operated by the Internet Security Research Group that underpins the trust for most Let’s Encrypt-issued TLS/SSL certificates used across the web.
- 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: Let’s Encrypt Authority X1 (via cross-signing chain) Target entity description: Let’s Encrypt Authority X1 (via cross-signing chain) is an intermediate certificate authority operated by Let’s Encrypt whose trust is anchored by the widely trusted DST Root CA X3, enabling free and automated TLS certificates for secure web connections.
-
A.
Let’s Encrypt R3 intermediate
chosen
The Let’s Encrypt R3 intermediate is a widely deployed intermediate certificate authority used by Let’s Encrypt to issue trusted TLS/SSL certificates for securing internet communications.
-
B.
Let’s Encrypt R3
Let’s Encrypt R3 is a widely used intermediate certificate authority operated by Let’s Encrypt under the ISRG Root X1 trust anchor to issue free, automated TLS/SSL certificates for secure web connections.
-
C.
Let’s Encrypt
Let’s Encrypt is a free, automated, and open certificate authority that provides TLS/SSL certificates to enable secure HTTPS connections for websites worldwide.
-
D.
DST Root CA X3
DST Root CA X3 is a widely trusted root certificate authority operated by IdenTrust that historically provided the cross-signed trust anchor enabling broad browser compatibility for Let’s Encrypt certificates.
-
E.
ISRG Root X1
ISRG Root X1 is the primary root certificate operated by the Internet Security Research Group that underpins the trust for most Let’s Encrypt-issued TLS/SSL certificates used across the web.
- F. None of above.
Provenance (2 batches)
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. |
| NER | Named-entity recognition | batch_69f15cb3deb88190874230ae06a352d6 |
completed | April 29, 2026, 1:19 a.m. |
Created at: April 16, 2026, 8:50 p.m.