Triple
T9931009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI 3-D Secure Core Security Standard |
E192647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | payment security standard |
C23213
|
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: payment security standard Context triple: [PCI 3-D Secure Core Security Standard, instanceOf, payment security standard]
-
A.
payment card security standard
chosen
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.
-
B.
payment application security standard
A payment application security standard is a set of formal requirements and best practices designed to ensure that software handling payment card data processes, stores, and transmits this information securely to prevent fraud and data breaches.
-
C.
payment card industry standard
A payment card industry standard is a set of technical and security requirements that govern how organizations accept, process, store, and transmit payment card data to reduce fraud and protect cardholder information.
-
D.
payment technology service
A payment technology service is a platform or system that enables the secure processing, authorization, and management of electronic financial transactions between payers, payees, and financial institutions.
-
E.
payment network
A payment network is a system of interconnected institutions, technologies, and rules that enables the authorization, clearing, and settlement of financial transactions between payers and payees.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:43 p.m.