Triple
T34985037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Authorization Board |
E1008921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FedRAMP governance body |
C17920
|
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 governance body Context triple: [Joint Authorization Board, instanceOf, FedRAMP governance body]
-
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.
federal oversight body
chosen
A federal oversight body is a government entity responsible for monitoring, evaluating, and enforcing compliance with laws, regulations, and standards across federal agencies or sectors to ensure accountability and integrity.
-
C.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
D.
Federal agency
A federal agency is a government organization established by national law to implement, administer, and enforce specific public policies and programs at the federal level.
-
E.
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.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.