Triple
T721375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cybersecurity Information Sharing Act of 2015 |
E14623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybersecurity law |
C3755
|
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: cybersecurity law Context triple: [Cybersecurity Information Sharing Act of 2015, instanceOf, cybersecurity law]
-
A.
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.
-
B.
counterterrorism law
Counterterrorism law is the body of domestic and international legal rules, procedures, and powers designed to prevent, investigate, and punish acts of terrorism while balancing national security with the protection of civil liberties and human rights.
-
C.
national security law
chosen
National security law is the body of legal rules, principles, and processes that govern how a state protects its national defense, intelligence, and foreign relations while balancing civil liberties and constitutional limits.
-
D.
privacy law
Privacy law is the body of legal rules and principles that governs the collection, use, storage, and disclosure of personal information to protect individuals’ privacy rights.
-
E.
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.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.