Triple
T28871524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Service Class Provider |
E732156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DICOM network role |
C24329
|
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: DICOM network role Context triple: [Service Class Provider, instanceOf, DICOM network role]
-
A.
DICOM concept
A DICOM concept is an abstract representation of a medical imaging-related entity, attribute, or relationship defined within the DICOM standard to enable consistent storage, exchange, and interpretation of clinical imaging information.
-
B.
medical imaging communication entity
chosen
A medical imaging communication entity is a system or component that creates, sends, receives, or processes medical imaging data and related information across healthcare networks.
-
C.
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.
-
D.
IHE profile family
An IHE profile family is a group of related IHE integration profiles that collectively address a specific clinical or workflow domain using consistent standards and design patterns.
-
E.
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.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:33 a.m.