Triple
T32498089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI SSC Code of Professional Responsibility |
E830580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | PCI SSC policy document |
C58524
|
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: PCI SSC policy document Context triple: [PCI SSC Code of Professional Responsibility, instanceOf, PCI SSC policy document]
-
A.
PCI SSC program document
chosen
A PCI SSC program document is an official publication issued by the PCI Security Standards Council that defines requirements, procedures, and guidance for participating organizations and stakeholders within a specific PCI compliance program.
-
B.
PCI SSC program
A PCI SSC program is an initiative or framework established by the Payment Card Industry Security Standards Council to develop, manage, and promote security standards and supporting resources that protect cardholder data and payment transactions.
-
C.
PCI SSC standard
The PCI SSC standard is a set of security requirements and guidelines established by the Payment Card Industry Security Standards Council to protect cardholder data and secure payment card transactions.
-
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.
payment card security standard
A payment card security standard is a set of technical and procedural requirements designed to protect cardholder data and secure payment card transactions from theft, fraud, and unauthorized access.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.