Triple
T29605686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Document Source |
E754570
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IHE XDS actor |
C54995
|
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: IHE XDS actor Context triple: [Document Source, instanceOf, IHE XDS actor]
-
A.
IHE profile family
An IHE profile family is a group of related IHE integration profiles that collectively address a specific clinical or workflow domain using consistent standards and design patterns.
-
B.
healthcare interoperability specification component
chosen
A healthcare interoperability specification component is a defined element (such as a data model, API, profile, or constraint) within a broader standard that enables consistent, secure, and semantically accurate exchange of health information across disparate systems.
-
C.
medical imaging communication entity
A medical imaging communication entity is a system or component that creates, sends, receives, or processes medical imaging data and related information across healthcare networks.
-
D.
NHS core system
The NHS core system is a centralized digital infrastructure that securely manages, integrates, and provides access to patient records, clinical workflows, and administrative services across the National Health Service.
-
E.
health information exchange backbone
A health information exchange backbone is the core infrastructure that securely connects disparate healthcare systems and organizations to enable standardized, real-time sharing of patient health data.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:25 p.m.