Triple
T38509545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Medicine radiation oncology department |
E921865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radiation oncology department |
C65070
|
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: radiation oncology department Context triple: [Penn Medicine radiation oncology department, instanceOf, radiation oncology department]
-
A.
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.
-
B.
pediatric cancer center
A pediatric cancer center is a specialized medical facility dedicated to diagnosing, treating, and supporting children and adolescents with cancer through multidisciplinary, family-centered care.
-
C.
radiation protection specialist
A radiation protection specialist monitors, evaluates, and controls exposure to ionizing and non-ionizing radiation to protect people, equipment, and the environment in medical, industrial, and research settings.
-
D.
ionizing radiation
Ionizing radiation is high-energy electromagnetic waves or particles that carry enough energy to remove tightly bound electrons from atoms or molecules, thereby ionizing them and potentially causing chemical and biological damage.
-
E.
cancer treatment protocol
A cancer treatment protocol is a structured, evidence-based plan that outlines the specific therapies, dosages, schedules, and monitoring procedures used to treat a particular type and stage of cancer.
- F. None of above. chosen
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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:32 p.m.