Triple
T21568320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerScribe |
E532217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radiology reporting solution |
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 reporting solution Context triple: [PowerScribe, instanceOf, radiology reporting solution]
-
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 survey
An imaging survey is a systematic observational study that captures images of a region of interest—such as the sky, a landscape, or biological tissue—using standardized instruments and methods to enable large-scale analysis and comparison.
-
C.
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.
-
D.
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.
-
E.
medical report
A medical report is a formal document that records a patient’s clinical history, examination findings, diagnostic test results, diagnoses, treatments, and recommendations for ongoing care.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:30 p.m.