Triple
T19436488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic Willow |
E486235
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Epic electronic health record |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Epic electronic health record | Statement: [Epic Willow, partOf, Epic electronic health record]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Epic electronic health record Context triple: [Epic Willow, partOf, Epic electronic health record]
-
A.
Regenstrief Medical Record System
The Regenstrief Medical Record System is an early, pioneering electronic medical record platform that helped shape modern health informatics and clinical data management practices.
-
B.
EpicCare Ambulatory
EpicCare Ambulatory is Epic Systems’ electronic health record module designed to support clinical workflows and documentation in outpatient and ambulatory care settings.
-
C.
Epic Clarity reporting database
Epic Clarity reporting database is Epic’s relational data warehouse optimized for complex clinical, financial, and operational reporting and analytics on data from the Epic electronic health record system.
-
D.
Fast Healthcare Interoperability Resources
Fast Healthcare Interoperability Resources (FHIR) is a modern, web-based standard for exchanging electronic healthcare information between systems in a consistent and interoperable way.
-
E.
Epic oncology suite
Epic oncology suite is Epic Systems’ integrated set of oncology-focused electronic health record tools designed to support cancer care workflows, including treatment planning, chemotherapy ordering, and patient management.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Epic electronic health record Target entity description: Epic electronic health record is a widely used, integrated healthcare software platform that manages clinical, administrative, and financial data across hospitals and health systems.
-
A.
Regenstrief Medical Record System
The Regenstrief Medical Record System is an early, pioneering electronic medical record platform that helped shape modern health informatics and clinical data management practices.
-
B.
EpicCare Ambulatory
chosen
EpicCare Ambulatory is Epic Systems’ electronic health record module designed to support clinical workflows and documentation in outpatient and ambulatory care settings.
-
C.
Epic Clarity reporting database
Epic Clarity reporting database is Epic’s relational data warehouse optimized for complex clinical, financial, and operational reporting and analytics on data from the Epic electronic health record system.
-
D.
Fast Healthcare Interoperability Resources
Fast Healthcare Interoperability Resources (FHIR) is a modern, web-based standard for exchanging electronic healthcare information between systems in a consistent and interoperable way.
-
E.
Epic oncology suite
Epic oncology suite is Epic Systems’ integrated set of oncology-focused electronic health record tools designed to support cancer care workflows, including treatment planning, chemotherapy ordering, and patient management.
- F. None of above.
Provenance (2 batches)
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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633618c2881908f3d2a9cabb02289 |
completed | April 20, 2026, 2:08 p.m. |
Created at: April 10, 2026, 1:38 p.m.