Triple
T16588717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Typologies Reports |
E403025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial crime analysis report |
C35411
|
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 analysis report Context triple: [Typologies Reports, instanceOf, financial crime analysis report]
-
A.
financial scandal
A financial scandal is a widely publicized incident in which individuals or organizations engage in unethical, illegal, or deceptive financial practices that result in significant economic harm, loss of trust, or legal consequences.
-
B.
criminal justice report
chosen
A criminal justice report is a formal document that records, analyzes, and communicates information about criminal incidents, investigations, legal proceedings, or correctional outcomes within the justice system.
-
C.
financial sector assessment report
A financial sector assessment report is a comprehensive analysis that evaluates the stability, performance, risks, and regulatory framework of a country’s financial system to inform policy decisions and reforms.
-
D.
risk and compliance data service
A risk and compliance data service aggregates, analyzes, and delivers regulatory, risk, and compliance-related information to help organizations identify exposures, meet legal obligations, and support informed governance decisions.
-
E.
corporate fraud case
A corporate fraud case is a legal action involving allegations that a company or its representatives intentionally deceived stakeholders for unlawful financial or competitive gain.
- 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.