Triple
T31587275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National University Health System |
E805988
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare cluster |
C46449
|
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: healthcare cluster Context triple: [National University Health System, instanceOf, healthcare cluster]
-
A.
healthcare innovation hub
A healthcare innovation hub is a collaborative ecosystem that brings together clinicians, researchers, entrepreneurs, and technologists to develop, test, and scale new solutions that improve health outcomes, patient experience, and system efficiency.
-
B.
academic health sciences cluster
chosen
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.
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.
-
D.
clinical care provider
A clinical care provider is a trained healthcare professional who assesses, diagnoses, treats, and manages patients’ health needs in clinical settings.
-
E.
healthcare services provider
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.
- 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.