Triple
T16588663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union anti-money laundering directives |
E403024
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-money laundering framework |
C3994
|
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: anti-money laundering framework Context triple: [European Union anti-money laundering directives, instanceOf, anti-money laundering framework]
-
A.
anti-money laundering initiative
An anti-money laundering initiative is a coordinated set of policies, procedures, and technologies designed to detect, prevent, and report the concealment of illicit funds within financial and commercial systems.
-
B.
anti–money laundering measure
chosen
An anti–money laundering measure is a policy, procedure, or control designed to detect, prevent, and report the concealment of illicitly obtained funds within the legitimate financial system.
-
C.
counter-terrorist financing initiative
A counter-terrorist financing initiative is a coordinated set of policies, processes, and tools designed to detect, prevent, and disrupt the flow of funds and financial support to terrorist organizations and activities.
-
D.
anti-fraud provision
An anti-fraud provision is a contractual or statutory clause designed to prevent, detect, and remedy deceptive or dishonest conduct in transactions or financial activities.
-
E.
compliance framework reference
A compliance framework reference is a structured guide that maps organizational policies, controls, and processes to specific regulatory or industry-standard requirements to ensure consistent adherence and auditability.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.