Triple
T31043193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mental Health Division |
E791051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare organization division |
C6306
|
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: healthcare organization division Context triple: [Mental Health Division, instanceOf, healthcare organization division]
-
A.
healthcare organization unit
chosen
A healthcare organization unit is a distinct administrative or functional division within a healthcare system (such as a department, clinic, or ward) that delivers specific health-related services, manages resources, and supports patient care processes.
-
B.
health care organization type
A health care organization type is a category that classifies organizations based on their structure, services, and role in delivering, financing, or coordinating health care.
-
C.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
D.
health management department
The health management department is responsible for planning, coordinating, and overseeing programs and services that promote, protect, and improve the health and well-being of individuals or populations within an organization or community.
-
E.
division of the United States Department of Health and Human Services
A division of the United States Department of Health and Human Services is an organizational unit within HHS responsible for administering specific health, human services, or regulatory programs in support of the department’s overall mission.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.