Triple
T29041277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Initiating Gateway |
E738002
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IHE XCPD actor |
C25020
|
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 XCPD actor Context triple: [Initiating Gateway, instanceOf, IHE XCPD 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.
health information exchange interoperability profile
chosen
A health information exchange interoperability profile is a standardized specification that defines how different healthcare systems and applications should structure, secure, and exchange electronic health data to ensure consistent, reliable, and seamless information sharing.
-
C.
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.
-
D.
IAVCEI program
The IAVCEI program is an organized framework of activities, initiatives, and resources coordinated by the International Association of Volcanology and Chemistry of the Earth's Interior to advance research, collaboration, and education in volcanology and related geosciences.
-
E.
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.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:02 a.m.