Triple
T28771754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certificate Enrollment Policy Web Service |
E726429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Active Directory Certificate Services component |
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: Active Directory Certificate Services component Context triple: [Certificate Enrollment Policy Web Service, instanceOf, Active Directory Certificate Services component]
-
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.
certificate status service
A certificate status service is a system that provides real-time information about the validity and revocation state of digital certificates to relying parties.
-
C.
Windows servicing model
The Windows servicing model is the structured process and schedule by which Microsoft delivers updates, patches, and feature enhancements to Windows operating systems throughout their lifecycle.
-
D.
DISA component
A DISA component is a modular element within the Defense Information Systems Agency’s infrastructure that provides specific communication, security, or information services to support Department of Defense operations.
-
E.
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.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:16 a.m.