Triple
T38017546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHS estate |
E948537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare infrastructure portfolio |
C15201
|
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 infrastructure portfolio Context triple: [NHS estate, instanceOf, healthcare infrastructure portfolio]
-
A.
healthcare infrastructure component
A healthcare infrastructure component is any physical, digital, or organizational element—such as facilities, equipment, information systems, or logistics—that collectively enables the delivery, coordination, and support of health services.
-
B.
Healthcare facility
A healthcare facility is an organized establishment where medical professionals provide preventive, diagnostic, therapeutic, and rehabilitative services to maintain or improve individuals' health.
-
C.
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.
-
D.
hospital system facilities
chosen
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital locations.
-
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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.