Triple
T5985384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Security Preservation Law |
E133213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security legislation |
C19707
|
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: security legislation Context triple: [Public Security Preservation Law, instanceOf, security legislation]
-
A.
national security law
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.
-
B.
national security law program
A national security law program is an academic or training course of study that focuses on the legal frameworks, institutions, and policies governing a nation’s defense, intelligence, and security operations.
-
C.
canonical legislation
Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
-
D.
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.
-
E.
security
Security is the conceptual class that encompasses mechanisms, policies, and practices designed to protect assets, information, and individuals from threats, vulnerabilities, and unauthorized access.
- F. None of above. chosen
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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:04 p.m.