Triple
T7961061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOC 2 |
E184865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | compliance framework |
C20031
|
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: compliance framework Context triple: [SOC 2, instanceOf, compliance framework]
-
A.
compliance platform
A compliance platform is an integrated system that centralizes, automates, and monitors an organization’s policies, controls, and regulatory obligations to ensure ongoing adherence to internal and external requirements.
-
B.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
C.
security management framework
chosen
A security management framework is a structured set of policies, processes, roles, and controls that organizations use to systematically identify, assess, manage, and monitor security risks to their information and assets.
-
D.
ISO framework
A structured, internationally recognized system of standards and guidelines developed by the International Organization for Standardization (ISO) to ensure quality, safety, efficiency, and interoperability across products, services, and processes.
-
E.
financial reporting framework
A financial reporting framework is a structured set of principles, standards, and rules that guide how an entity measures, recognizes, presents, and discloses financial information in its financial statements.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:12 p.m.