Triple
T21602574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Health Partners |
E533083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional health network |
C30046
|
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: regional health network Context triple: [Premier Health Partners, instanceOf, regional health network]
-
A.
regional hospital system
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.
-
B.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
C.
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.
-
D.
healthcare provider network
chosen
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.
-
E.
regional chapter network
A regional chapter network is a coordinated system of local chapters within a defined geographic area that collaborate under a shared mission, governance structure, and resource framework to advance common goals.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:33 p.m.