Triple

T28033440
Position Surface form Disambiguated ID Type / Status
Subject SOC 3 E708333 entity
Predicate instanceOf P0 FINISHED
Object Service Organization Control report C53703 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: Service Organization Control report
Context triple: [SOC 3, instanceOf, Service Organization Control report]
  • A. 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.
  • B. service supervision suite
    A service supervision suite is a coordinated set of tools and processes that continuously monitor, manage, and automatically recover services to ensure reliability, performance, and minimal downtime.
  • C. application service organization
    An application service organization is a business entity that delivers software applications and related IT services to clients, typically over a network, managing deployment, maintenance, and support on their behalf.
  • D. risk and compliance data service
    A risk and compliance data service aggregates, analyzes, and delivers regulatory, risk, and compliance-related information to help organizations identify exposures, meet legal obligations, and support informed governance decisions.
  • E. security management service
    A security management service is a system or organization that plans, implements, monitors, and continuously improves measures to protect an entity’s assets, information, and operations from security threats and vulnerabilities.
  • F. None of above. chosen

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_69ef9b6bdd9c8190bb3a574a03774ad1 completed April 27, 2026, 5:22 p.m.
Created at: April 27, 2026, 8:18 p.m.