Triple
T28871716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM structured reports |
E732160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standardized healthcare document |
C55329
|
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: standardized healthcare document Context triple: [DICOM structured reports, instanceOf, standardized healthcare document]
-
A.
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.
-
B.
healthcare entitlement document
A healthcare entitlement document is an official record that grants an individual the right to access specified healthcare services, benefits, or coverage under a particular health program or policy.
-
C.
standardized legal document
A standardized legal document is a pre-formatted, legally binding template with uniform structure and language designed for repeated use in similar transactions or situations.
-
D.
NHS document
An NHS document is an official record or communication produced by the National Health Service that contains healthcare-related information, guidance, or data for patients, staff, or partner organizations.
-
E.
electronic health record system
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.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 7:33 a.m.