Triple
T9314502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Environmental Information Regulations 2004 |
E224084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | access to information law |
C3936
|
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: access to information law Context triple: [Environmental Information Regulations 2004, instanceOf, access to information law]
-
A.
freedom of information law
chosen
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.
-
B.
law library
A law library is a specialized collection of legal resources, including statutes, case law, regulations, and secondary sources, organized to support legal research and practice.
-
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.
legislative information system
A legislative information system is a digital platform that collects, manages, tracks, and provides access to legislative documents, processes, and activities to support lawmakers, staff, and the public.
-
E.
legal information category
A legal information category is a classification that organizes legal content—such as statutes, case law, regulations, or legal commentary—into distinct, searchable groupings based on subject matter, jurisdiction, or document type.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.