Triple

T35406195
Position Surface form Disambiguated ID Type / Status
Subject FedRAMP Marketplace package E1023368 entity
Predicate instanceOf P0 FINISHED
Object FedRAMP documentation package C64207 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 documentation package
Context triple: [FedRAMP Marketplace package, instanceOf, FedRAMP documentation package]
  • 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. security authorization documentation bundle chosen
    A security authorization documentation bundle is a curated set of formal records, assessments, approvals, and supporting evidence that collectively demonstrate a system’s compliance with defined security requirements and justify its authorization to operate.
  • C. legal framework for federal information resources management
    A legal framework for federal information resources management is the set of laws, regulations, and policies that govern how federal agencies plan, acquire, secure, use, share, and dispose of information and information technology to ensure efficiency, accountability, and protection of government data and services.
  • D. PCI DSS assessment document
    A PCI DSS assessment document is a formal report that evaluates and records an organization’s compliance status with the Payment Card Industry Data Security Standard requirements.
  • E. 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.
  • 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.