Triple
T8283777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Payment Application Data Security Standard |
E193742
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | payment card industry standard |
C23809
|
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 card industry standard Context triple: [Payment Application Data Security Standard, instanceOf, payment card industry standard]
-
A.
payment network
A payment network is a system that facilitates the authorization, clearing, and settlement of financial transactions between payers, payees, and their financial institutions.
-
B.
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.
-
C.
payment technology company
A payment technology company develops and provides digital infrastructure, platforms, and tools that enable secure, efficient, and seamless financial transactions between businesses, consumers, and financial institutions.
-
D.
payment network operator
A payment network operator is an entity that manages and maintains the infrastructure, rules, and processes that enable electronic payment transactions to be routed, authorized, cleared, and settled between financial institutions and merchants.
-
E.
magnetic stripe card
A magnetic stripe card is a plastic card that stores data in a magnetizable stripe on its surface, enabling electronic reading for identification, access control, or financial transactions.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:52 p.m.