Triple
T31586616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SingHealth |
E805972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public healthcare cluster |
C26598
|
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: public healthcare cluster Context triple: [SingHealth, instanceOf, public healthcare cluster]
-
A.
healthcare-related social network
A healthcare-related social network is an online platform that connects patients, caregivers, and healthcare professionals to share experiences, support, and information about health conditions and treatments.
-
B.
academic health sciences cluster
An academic health sciences cluster is a collaborative organizational structure that brings together universities, teaching hospitals, research institutes, and related partners to integrate education, research, and clinical care in the health sciences.
-
C.
community health center
A community health center is a local, patient-centered facility that provides accessible, comprehensive primary and preventive healthcare services, often focusing on underserved populations regardless of their ability to pay.
-
D.
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.
-
E.
public hospital network
chosen
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.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:26 p.m.