Triple
T16703462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OECD Anti-Bribery Convention monitoring reports |
E405904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-corruption monitoring instrument |
C7800
|
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-corruption monitoring instrument Context triple: [OECD Anti-Bribery Convention monitoring reports, instanceOf, anti-corruption monitoring instrument]
-
A.
anti-corruption instrument
chosen
An anti-corruption instrument is a policy, mechanism, or tool designed to prevent, detect, and sanction corrupt practices within public or private institutions.
-
B.
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.
-
C.
anti-corruption investigation
An anti-corruption investigation is a systematic inquiry conducted to uncover, document, and address instances of bribery, fraud, abuse of power, or other corrupt practices within public or private institutions.
-
D.
monitoring mechanism
A monitoring mechanism is a system or process that continuously observes, measures, and evaluates activities or conditions to detect deviations, ensure compliance, and support timely decision-making.
-
E.
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.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.