Triple
T34577363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton University Proton Therapy Institute |
E887796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proton therapy center |
C41365
|
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: proton therapy center Context triple: [Hampton University Proton Therapy Institute, instanceOf, proton therapy center]
-
A.
radiation oncology department
A radiation oncology department is a specialized medical unit where multidisciplinary teams plan and deliver targeted radiation treatments to diagnose, manage, and cure cancer and certain benign conditions while minimizing harm to healthy tissues.
-
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.
tertiary care center
A tertiary care center is a specialized healthcare facility that provides advanced, highly specialized diagnostic, therapeutic, and surgical services typically unavailable at primary or secondary care institutions.
-
D.
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.
-
E.
specialty medical center
chosen
A specialty medical center is a healthcare facility focused on diagnosing, treating, and managing conditions within a specific medical field or group of related specialties, often offering advanced expertise and technology.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.