Triple
T1542024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia Municipal Regulations |
E32889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative regulations |
C4489
|
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: administrative regulations Context triple: [District of Columbia Municipal Regulations, instanceOf, administrative regulations]
-
A.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
-
B.
administrative code
chosen
Administrative code is a structured set of rules and regulations issued by governmental or organizational authorities to guide, control, and standardize administrative actions and procedures.
-
C.
administrative oversight regime
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
D.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
E.
administrative tribunal
An administrative tribunal is a specialized quasi-judicial body that resolves disputes and makes determinations arising from the decisions or actions of government agencies under specific statutory frameworks.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.