Triple
T37001147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton regional health system |
E915352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated health network |
C28961
|
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: integrated health network Context triple: [Hamilton regional health system, instanceOf, integrated health network]
-
A.
public hospital network
A public hospital network is a coordinated system of government-funded hospitals and healthcare facilities that collaboratively provide accessible, often low-cost or free, medical services to a defined population or region.
-
B.
healthcare provider network
A healthcare provider network is an organized group of doctors, hospitals, and other medical professionals and facilities that contract with a health plan to deliver coordinated care to its members.
-
C.
Integrated Care Boards
Integrated Care Boards are statutory NHS organizations in England responsible for planning, funding, and coordinating health and care services across local systems to improve population health and reduce inequalities.
-
D.
regional hospital system
chosen
A regional hospital system is an organized network of hospitals and related healthcare facilities within a specific geographic area that coordinates services, resources, and administration to provide comprehensive medical care to the local 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.