Triple
T26148439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goulburn Valley Health |
E659745
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional health service |
C31723
|
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 service Context triple: [Goulburn Valley Health, instanceOf, regional health service]
-
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 government service
A regional government service is an administrative entity that delivers public programs, resources, and regulatory functions within a specific geographic area under the authority of a higher-level government.
-
C.
healthcare services provider
chosen
A healthcare services provider is an organization or individual that delivers medical, therapeutic, or preventive health services to patients to diagnose, treat, and manage health conditions.
-
D.
Healthcare service
A healthcare service is an organized set of medical and supportive activities provided by professionals and institutions to promote, maintain, or restore individuals’ health and well-being.
-
E.
healthcare administration service
A healthcare administration service manages the non-clinical operations of healthcare organizations, including scheduling, billing, compliance, records management, and coordination among providers, payers, and patients to ensure efficient and compliant delivery of care.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
Created at: April 26, 2026, 8:23 p.m.