Triple
T25781902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial College Healthcare NHS Trust |
E649312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NHS trust |
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: NHS trust Context triple: [Imperial College Healthcare NHS Trust, instanceOf, NHS trust]
-
A.
NHS core system
The NHS core system is a centralized digital infrastructure that securely manages, integrates, and provides access to patient records, clinical workflows, and administrative services across the National Health Service.
-
B.
NHS document
An NHS document is an official record or communication produced by the National Health Service that contains healthcare-related information, guidance, or data for patients, staff, or partner organizations.
-
C.
mental health trust
A mental health trust is a specialized healthcare organization within the UK’s National Health Service that provides assessment, treatment, and support services for people with mental health conditions in a defined geographic area.
-
D.
NHS indemnity scheme
The NHS indemnity scheme is a government-backed arrangement that provides legal and financial protection to NHS staff and organisations against claims arising from clinical negligence and certain non-clinical incidents in the course of their work.
-
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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:39 a.m.