Triple
T28871427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Message Service Element |
E732154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | DICOM upper layer service |
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 upper layer service Context triple: [DICOM Message Service Element, instanceOf, DICOM upper layer service]
-
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.
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.
-
D.
image acquisition standard
An image acquisition standard is a defined set of rules and protocols that ensure consistent, interoperable, and high-quality capture of images across different devices, systems, and workflows.
-
E.
extension of Picture Transfer Protocol
An extension of Picture Transfer Protocol is an enhanced communication framework that builds on PTP to support additional media types, metadata, and advanced device control features beyond basic image transfer.
- 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.