Triple
T28526122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the State Health Planning and Development Agency of the District of Columbia |
E721908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health planning agency |
C20647
|
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: health planning agency Context triple: [Office of the State Health Planning and Development Agency of the District of Columbia, instanceOf, health planning agency]
-
A.
health agency
chosen
A health agency is an organization responsible for planning, coordinating, and delivering public health services, policies, and programs to protect and improve the health of a population.
-
B.
planning agency
A planning agency is an organization responsible for developing, coordinating, and regulating plans and policies to guide land use, infrastructure, and community development within a specific jurisdiction.
-
C.
regional planning agency
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
-
D.
health authority
A health authority is an organization or governmental body responsible for overseeing, regulating, and coordinating public health services, policies, and programs within a specific jurisdiction.
-
E.
health policy department
A health policy department is an organizational unit responsible for researching, developing, analyzing, and advising on policies that shape healthcare systems, public health initiatives, and regulatory 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:24 a.m.