Triple
T26463236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit for the Coordination of Fraud Prevention |
E665690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-fraud body |
C38064
|
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-fraud body Context triple: [Unit for the Coordination of Fraud Prevention, instanceOf, anti-fraud body]
-
A.
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.
-
B.
anti-money laundering body type
chosen
An anti-money laundering body type is an organizational entity, such as a regulatory authority or compliance unit, responsible for detecting, preventing, and reporting money laundering and related financial crimes within its jurisdiction or institution.
-
C.
anti-corruption organization
An anti-corruption organization is an entity dedicated to preventing, investigating, and exposing corrupt practices while promoting transparency, accountability, and integrity in public and private institutions.
-
D.
anti-doping body
An anti-doping body is an organization responsible for developing, implementing, and enforcing rules and procedures to prevent and detect the use of prohibited performance-enhancing substances and methods in sport.
-
E.
fraudster
A fraudster is an individual who intentionally deceives others, typically for financial or personal gain, by using false representations, manipulations, or dishonest schemes.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:14 a.m.