Triple
T26652314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NWAS |
E669096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Health Service trust |
C51869
|
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: National Health Service trust Context triple: [NWAS, instanceOf, National Health Service trust]
-
A.
component of Integrated Care System in England
A component of an Integrated Care System in England is an organizational or functional unit (such as NHS providers, local authorities, or voluntary sector partners) that collaborates to plan, fund, and deliver coordinated health and care services for a defined population.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
public hospital network
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. chosen
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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:33 a.m.