Triple
T8194707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia health and human services system |
E191399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public service system |
C23643
|
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: public service system Context triple: [District of Columbia health and human services system, instanceOf, public service system]
-
A.
public service mission
A public service mission is a guiding purpose or mandate focused on delivering benefits, support, or protections to the public or a specific community, typically through government or nonprofit actions that prioritize the common good over private gain.
-
B.
through service
A through service is a transportation offering in which a vehicle or passenger travels from origin to destination across one or more intermediate points without requiring a transfer or change of service.
-
C.
public emergency service system
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
D.
public service facility
A public service facility is a place or infrastructure provided by government or community organizations to deliver essential services such as health, safety, education, or administration to the public.
-
E.
service book
A service book is a record that documents the maintenance, repairs, and servicing history of an item, typically a vehicle or machine, to ensure proper upkeep and verify its condition over time.
- 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:42 p.m.