Triple
T23313480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Inc. v. Levinson |
E590642
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | class action securities fraud case |
C33766
|
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: class action securities fraud case Context triple: [Basic Inc. v. Levinson, instanceOf, class action securities fraud case]
-
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.
racketeering case
A racketeering case is a legal action in which prosecutors allege that individuals or organizations engaged in a pattern of criminal activity as part of an enterprise, often under statutes like RICO.
-
C.
U.S. Securities and Exchange Commission procedure
U.S. Securities and Exchange Commission procedure refers to the formal processes, rules, and steps the SEC follows to regulate securities markets, enforce federal securities laws, review filings, and conduct investigations and administrative actions.
-
D.
federal civil enforcement action
A federal civil enforcement action is a non-criminal lawsuit brought by a U.S. federal agency or the Department of Justice to compel compliance with federal laws, regulations, or orders and to obtain remedies such as injunctions, penalties, or restitution.
-
E.
class action case
chosen
A class action case is a legal proceeding in which one or more plaintiffs file a lawsuit on behalf of a larger group of people who share similar claims against the same defendant.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.