Triple
T21774223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Collaboration with Systems for Health HR Networks |
E537524
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health systems unit |
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: health systems unit Context triple: [Centre for Collaboration with Systems for Health HR Networks, instanceOf, health systems unit]
-
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.
hospital system facilities
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital locations.
-
C.
medical system
A medical system is an organized framework of people, institutions, technologies, and processes that work together to deliver healthcare services for maintaining and improving individuals’ health.
-
D.
health care system
A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
-
E.
public health system
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:51 p.m.