Triple
T25159161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summary Care Record |
E626394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electronic patient record |
C16823
|
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: electronic patient record Context triple: [Summary Care Record, instanceOf, electronic patient record]
-
A.
electronic health record system
chosen
An electronic health record system is a digital platform that securely collects, stores, manages, and shares patients’ health information to support clinical care, coordination, and decision-making.
-
B.
clinical documentation solution
A clinical documentation solution is a software system that streamlines the creation, management, and secure storage of patient health records to improve accuracy, efficiency, and compliance in healthcare settings.
-
C.
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.
-
D.
electronic court records system
An electronic court records system is a digital platform that securely stores, manages, and provides controlled access to court case documents, filings, and related judicial information.
-
E.
medical report
A medical report is a formal document that records a patient’s clinical history, examination findings, diagnostic test results, diagnoses, treatments, and recommendations for ongoing care.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.