Triple
T14450498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dow Jones Risk & Compliance |
E358318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial crime compliance solution |
C13165
|
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: financial crime compliance solution Context triple: [Dow Jones Risk & Compliance, instanceOf, financial crime compliance solution]
-
A.
compliance platform
chosen
A compliance platform is an integrated system that centralizes, automates, and monitors an organization’s policies, controls, and regulatory obligations to ensure ongoing adherence to internal and external requirements.
-
B.
anti–money laundering measure
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.
tax compliance solution
A tax compliance solution is a system that automates the calculation, reporting, and filing of taxes to ensure organizations meet all regulatory requirements accurately and on time.
-
D.
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.
-
E.
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.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.