Triple
T36166580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhonda Fleming Mann Resource Center for Women with Cancer at UCLA |
E1046017
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | patient resource center |
C45270
|
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: patient resource center Context triple: [Rhonda Fleming Mann Resource Center for Women with Cancer at UCLA, instanceOf, patient resource center]
-
A.
patient portal
A patient portal is a secure online platform that allows patients to access their personal health information, communicate with healthcare providers, manage appointments, and perform other health-related tasks.
-
B.
health information centre
chosen
A health information centre is a dedicated facility or service that provides individuals with reliable, accessible, and up-to-date information, guidance, and resources on health, wellness, and medical services.
-
C.
clinical resource
A clinical resource is any tool, material, information source, or service used by healthcare professionals to support patient care, decision-making, and clinical operations.
-
D.
patient demographics service
A patient demographics service manages and provides access to core patient identity and background information—such as name, date of birth, contact details, and other non-clinical attributes—across healthcare systems.
-
E.
patient model
A patient model is a structured representation of an individual receiving healthcare, capturing their demographic, clinical, and treatment-related data to support medical decision-making and care management.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.