Triple
T25820693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Congress of Radiology |
E650395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radiology conference |
C6882
|
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 conference Context triple: [European Congress of Radiology, instanceOf, radiology conference]
-
A.
medical imaging communication entity
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.
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.
health conference
chosen
A health conference is a structured event where healthcare professionals, researchers, policymakers, and stakeholders gather to share knowledge, discuss current issues, and explore innovations in health and medicine.
-
E.
radiation oncology journal
A radiation oncology journal is a peer-reviewed periodical that publishes research, reviews, and clinical reports on the use of radiation therapy in the diagnosis, treatment, and management of cancer and related diseases.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:29 a.m.