Triple
T22499157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DST Root CA X3 |
E556221
|
entity |
| Predicate | enabledBroadBrowserCompatibilityFor |
P92937
|
FINISHED |
| Object | Let’s Encrypt certificates |
—
|
LITERAL FINISHED |
How this triple was built (2 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 certificates | Statement: [DST Root CA X3, enabledBroadBrowserCompatibilityFor, Let’s Encrypt certificates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enabledBroadBrowserCompatibilityFor Context triple: [DST Root CA X3, enabledBroadBrowserCompatibilityFor, Let’s Encrypt certificates]
-
A.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
-
B.
isBroad
Indicates that something has a large width or extensive scope relative to a reference or context.
-
C.
isGenerallyCompatibleWith
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
-
D.
boostCompatibility
chosen
Indicates that one entity enhances or improves how well another entity works, interacts, or fits together with a given system, standard, or counterpart.
-
E.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
- F. None of above.
Provenance (3 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. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.