Triple
T3925519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Human Services Agency |
E93265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public social services agency |
C14602
|
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 social services agency Context triple: [San Francisco Human Services Agency, instanceOf, public social services agency]
-
A.
child protective services agency
A child protective services agency is a government or authorized organization responsible for investigating reports of child abuse or neglect and ensuring the safety, welfare, and permanency of children through protective interventions and support services.
-
B.
child support agency
A child support agency is an organization that helps establish, enforce, and manage financial and related support obligations for children, typically by working with parents, courts, and other authorities.
-
C.
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.
-
D.
settlement house
A settlement house is a community-based center, typically in an urban, low-income neighborhood, that provides social services, education, and cultural programs to support and empower local residents.
-
E.
public safety agency
A public safety agency is an organization responsible for protecting the public from threats and hazards by preventing, responding to, and managing emergencies, crimes, and disasters within a community or jurisdiction.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:23 p.m.