Triple
T3777622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT scanner |
E83345
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical imaging device |
C6456
|
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 device Context triple: [CT scanner, instanceOf, medical imaging device]
-
A.
medical device
chosen
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.
-
B.
portable medical device
A portable medical device is a compact, self-contained piece of medical equipment designed to be easily transported and used in various settings to monitor, diagnose, or treat patients outside traditional clinical environments.
-
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.
imaging preparation method
An imaging preparation method is a systematic procedure used to treat, condition, or configure a sample, subject, or environment to enable or enhance the acquisition of meaningful images by an imaging system.
-
E.
medical technology division
A medical technology division is an organizational unit within a healthcare or life sciences entity responsible for developing, evaluating, and managing medical devices, diagnostic tools, and related technologies to support clinical care and research.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:36 p.m.