Triple
T6409086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 10(b) of the Securities Exchange Act of 1934 |
E127660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-fraud provision |
C20089
|
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 provision Context triple: [Section 10(b) of the Securities Exchange Act of 1934, instanceOf, anti-fraud provision]
-
A.
safeguard measure provision
A safeguard measure provision is a legal clause that allows temporary restrictions or corrective actions to protect a party’s interests when unexpected or harmful circumstances arise under an agreement or regulatory framework.
-
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.
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.
-
D.
anti-corruption instrument
An anti-corruption instrument is a policy, mechanism, or tool designed to prevent, detect, and sanction corrupt practices within public or private institutions.
-
E.
anti-discrimination measure
An anti-discrimination measure is a policy, law, or practice designed to prevent, reduce, or remedy unequal treatment of individuals or groups based on protected characteristics such as race, gender, age, disability, religion, or sexual orientation.
- F. None of above. chosen
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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:41 p.m.