Triple
T35406054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP Agency ATO |
E1023365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FedRAMP authorization type |
C32459
|
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: FedRAMP authorization type Context triple: [FedRAMP Agency ATO, instanceOf, FedRAMP authorization type]
-
A.
FedRAMP impact level
A FedRAMP impact level is a classification that defines the potential risk and security requirements for a cloud system based on the sensitivity and criticality of the federal information it processes, stores, or transmits.
-
B.
Provisional Authority to Operate
chosen
A Provisional Authority to Operate is a temporary, risk-managed authorization granted to an information system to operate under defined conditions while it completes required security and compliance activities.
-
C.
Zero Trust Architecture standard
A Zero Trust Architecture standard defines a security framework that assumes no implicit trust in any user, device, or network component and enforces continuous verification, least-privilege access, and strict segmentation to protect resources.
-
D.
Authenticator Assurance Level
Authenticator Assurance Level is a measure of the strength and reliability of an authentication process, indicating the degree of confidence that the user’s claimed identity is accurate based on the types and combinations of authenticators used.
-
E.
SOC 2 report type
A SOC 2 report type is a standardized assurance report that evaluates and documents how a service organization’s controls meet predefined trust service criteria (such as security, availability, processing integrity, confidentiality, and privacy), with Type I assessing design at a point in time and Type II assessing design and operating effectiveness over a period.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.