Triple
T12109584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computer Fraud and Abuse Act |
E288387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computer crime law |
C27155
|
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: computer crime law Context triple: [Computer Fraud and Abuse Act, instanceOf, computer crime law]
-
A.
computing law
Computing law is the body of legal principles, regulations, and case law that governs the development, use, and impact of computer technologies, software, data, and digital networks.
-
B.
criminal code
A criminal code is a systematic collection of laws that define criminal offenses, prescribe penalties, and establish rules for prosecution and punishment within a jurisdiction.
-
C.
intelligence law
Intelligence law is the body of legal rules, principles, and oversight mechanisms that govern the collection, analysis, sharing, and use of intelligence by state and related actors to protect national security while safeguarding rights and liberties.
-
D.
specialized criminal law
chosen
Specialized criminal law is a focused area of legal practice that deals with specific categories of criminal offenses, such as white-collar crime, cybercrime, or organized crime, requiring in-depth expertise in the relevant statutes, procedures, and investigative methods.
-
E.
criminal justice information system
A criminal justice information system is an integrated platform that collects, manages, and shares data related to crimes, offenders, victims, and justice processes among law enforcement, courts, and correctional agencies.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.