Triple
T31639464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Stock Exchange fraud of 1814 |
E807405
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | securities fraud |
C5265
|
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: securities fraud Context triple: [London Stock Exchange fraud of 1814, instanceOf, securities fraud]
-
A.
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.
-
B.
financial scandal
chosen
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.
-
C.
securities commission
A securities commission is a government or regulatory authority responsible for overseeing and enforcing laws governing securities markets to protect investors and ensure fair, transparent, and efficient trading.
-
D.
securities regulation law
Securities regulation law is the body of rules and principles governing the issuance, trading, disclosure, and oversight of financial instruments such as stocks and bonds to protect investors and maintain fair, efficient markets.
-
E.
mail fraud case
A mail fraud case involves a legal action in which an individual or entity is accused of using postal or delivery services as part of a scheme to intentionally deceive others for financial or personal 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:48 p.m.