Triple
T28872919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIS |
E732181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Radiology information system |
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: Radiology information system Context triple: [RIS, instanceOf, Radiology information system]
-
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.
medical system
A medical system is an organized framework of people, institutions, technologies, and processes that work together to deliver healthcare services for maintaining and improving individuals’ health.
-
C.
medical imaging procedure
A medical imaging procedure is a clinical process that uses specialized equipment and techniques to create visual representations of internal body structures and functions for diagnosis, monitoring, or treatment planning.
-
D.
electronic health record system
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.
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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:34 a.m.