Triple
T3828764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Information Security Modernization Act of 2014 |
E88756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information security law |
C5533
|
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: information security law Context triple: [Federal Information Security Modernization Act of 2014, instanceOf, information security 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.
information security standard
chosen
An information security standard is a formalized set of policies, procedures, and controls designed to protect information assets by defining consistent requirements for confidentiality, integrity, and availability.
-
C.
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.
-
D.
information system
An information system is an organized combination of people, processes, data, and technology designed to collect, process, store, and distribute information to support decision-making and control in an organization.
-
E.
freedom of information law
Freedom of information law is a legal framework that grants the public the right to access records held by government bodies, subject to specific exemptions for privacy, security, and other protected interests.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.