Triple
T25159162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summary Care Record |
E626394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NHS information system |
C16823
|
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 information system Context triple: [Summary Care Record, instanceOf, NHS information system]
-
A.
NIH information system
An NIH information system is an integrated digital platform that manages, stores, and facilitates secure access to biomedical research data, administrative records, and operational information across the National Institutes of Health.
-
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.
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.
-
D.
electronic health record system
chosen
An electronic health record system is a digital platform that securely collects, stores, manages, and shares patients’ health information to support clinical care, coordination, and decision-making.
-
E.
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.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.