Triple
T26627786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Freedom of Information Act |
E668404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open records 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: open records law Context triple: [District of Columbia Freedom of Information Act, instanceOf, open records law]
-
A.
open meeting law
Open meeting law is a legal framework that requires governmental or public bodies to conduct their meetings transparently, with advance notice and public access, to ensure accountability and prevent secret decision-making.
-
B.
legal record
A legal record is an official document or collection of documents that formally captures, preserves, and provides evidence of legal actions, decisions, rights, and obligations.
-
C.
public disclosure system
A public disclosure system is a structured mechanism for collecting, verifying, and openly publishing information so that stakeholders and the general public can access and evaluate it for transparency and accountability.
-
D.
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.
-
E.
official record system
An official record system is a structured, authoritative repository and management framework for creating, storing, tracking, and preserving formal documents and data that serve as the definitive source of truth for an organization or jurisdiction.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:23 a.m.