Triple
T8755674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSG |
E208066
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | IHE XDS profile |
E732170
|
NE FINISHED |
How this triple was built (2 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: IHE XDS profile | Statement: [DSG, relatedTo, IHE XDS profile]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IHE XDS profile Context triple: [DSG, relatedTo, IHE XDS profile]
-
A.
IHE XDS
chosen
IHE XDS (Cross-Enterprise Document Sharing) is a healthcare IT profile that enables standardized, secure sharing and retrieval of clinical documents across different healthcare organizations and systems.
-
B.
IHE profile XUA
IHE profile XUA (Cross-Enterprise User Assertion) is an Integrating the Healthcare Enterprise specification that defines how to securely communicate authenticated user identity and role information across healthcare systems for access control and auditing.
-
C.
IHE Patient Care Device profiles
IHE Patient Care Device profiles are interoperability specifications that define how medical devices integrate and exchange data within healthcare IT systems to support safe, coordinated patient care.
-
D.
IHE ATNA
IHE ATNA (Audit Trail and Node Authentication) is an IHE integration profile that defines standards for secure node authentication and comprehensive auditing of security-relevant events in healthcare IT systems.
-
E.
IHE Technical Framework
The IHE Technical Framework is a set of detailed interoperability specifications and implementation guidelines developed by Integrating the Healthcare Enterprise to enable consistent, standards-based information exchange across healthcare systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf519175248190b53c8958cfeeebfa |
completed | April 3, 2026, 5:35 a.m. |
Created at: March 30, 2026, 6:39 p.m.