Triple
T26492725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doppler ultrasound |
E669200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical imaging technique |
C36768
|
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 technique Context triple: [Doppler ultrasound, instanceOf, medical imaging technique]
-
A.
medical imaging procedure
chosen
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.
-
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.
medical technology
Medical technology encompasses the tools, devices, software, and procedures used to prevent, diagnose, monitor, and treat health conditions, improving patient outcomes and healthcare delivery.
-
D.
computed tomography concept
A computed tomography concept represents the abstract idea, parameters, and relationships underlying CT imaging processes, including image acquisition, reconstruction, interpretation, and associated clinical or technical attributes.
-
E.
optical imaging method
An optical imaging method is a technique that uses light and its interactions with matter to noninvasively capture, visualize, and analyze structural or functional information about an object or sample.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:05 a.m.