Triple
T30356434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primary Care Trusts in the NHS in England and Wales |
E772154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | primary care 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: primary care trust Context triple: [Primary Care Trusts in the NHS in England and Wales, instanceOf, primary care trust]
-
A.
National Health Service trust
chosen
A National Health Service trust is an organizational unit within the UK's NHS responsible for managing and delivering specific healthcare services, such as hospital, community, or mental health care, within a defined area or specialty.
-
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.
tertiary care center
A tertiary care center is a specialized healthcare facility that provides advanced, highly specialized diagnostic, therapeutic, and surgical services typically unavailable at primary or secondary care institutions.
-
D.
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.
-
E.
clinical care provider
A clinical care provider is a trained healthcare professional who assesses, diagnoses, treats, and manages patients’ health needs in clinical settings.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:57 p.m.