Triple
T12534575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthanc |
E299654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical imaging software |
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: medical imaging software Context triple: [Orthanc, instanceOf, medical imaging software]
-
A.
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.
-
B.
imaging architecture
Imaging architecture is the conceptual and technical framework that defines how imaging components, data flows, and processing pipelines are organized and integrated to capture, transform, analyze, and deliver visual information.
-
C.
mobile imaging technology
Mobile imaging technology encompasses portable, often handheld devices and systems that capture, process, and transmit visual or sensor-based images for applications such as diagnostics, surveillance, mapping, and consumer photography.
-
D.
medical device
A medical device is any instrument, apparatus, machine, implant, or similar article intended for use in diagnosing, preventing, monitoring, treating, or alleviating disease or other medical conditions in humans or animals.
-
E.
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.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.