Triple
T24922999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation E |
E618776
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electronic fund transfer regulation |
C19622
|
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: electronic fund transfer regulation Context triple: [Regulation E, instanceOf, electronic fund transfer regulation]
-
A.
electronic payment system
An electronic payment system is a digital infrastructure that enables the secure transfer of funds between parties via electronic devices and networks without the need for physical cash or paper-based instruments.
-
B.
electronic business standard
An electronic business standard is a formally defined set of rules, formats, and protocols that enable consistent, interoperable electronic transactions and data exchange between organizations.
-
C.
clearing and settlement system
A clearing and settlement system is an infrastructure that validates, matches, nets, and finalizes financial transactions between parties, ensuring accurate transfer of securities and funds and mitigation of counterparty risk.
-
D.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
E.
economic regulation
chosen
Economic regulation is the set of laws, rules, and administrative actions through which governments influence, control, or guide economic activity, markets, and business behavior to achieve public policy objectives.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:29 a.m.