Triple
T8521965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHE Laboratory |
E201712
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | IHE IT Infrastructure |
E38997
|
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 IT Infrastructure | Statement: [IHE Laboratory, relatedTo, IHE IT Infrastructure]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IHE IT Infrastructure Context triple: [IHE Laboratory, relatedTo, IHE IT Infrastructure]
-
A.
IHE IT Infrastructure profiles
chosen
IHE IT Infrastructure profiles are a set of interoperability specifications that define how healthcare IT systems securely exchange, manage, and share health information across institutions and platforms.
-
B.
IHE
IHE is a global healthcare initiative that promotes the coordinated use of established standards to improve the interoperability of health information systems.
-
C.
IHE Laboratory
IHE Laboratory is a domain within the Integrating the Healthcare Enterprise initiative that defines standards-based profiles to improve interoperability and information exchange in clinical laboratory workflows.
-
D.
IHE XCA
IHE XCA (Cross-Community Access) is an IHE integration profile that defines how healthcare organizations in different communities securely discover and retrieve patients’ clinical documents across organizational and regional boundaries.
-
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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe62a490481908ee0ad4ba9a94682 |
completed | March 31, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6d3fabb08190a3ad63f9153ad44c |
completed | April 2, 2026, 1:21 p.m. |
Created at: March 30, 2026, 6:16 p.m.