Triple
T4617049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union medical device regulations |
E100892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical device regulation system |
C16105
|
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: medical device regulation system Context triple: [European Union medical device regulations, instanceOf, medical device regulation system]
-
A.
medical device
A medical device is any instrument, apparatus, machine, implant, or similar article intended for use in diagnosing, preventing, monitoring, treating, or alleviating disease or other medical conditions in humans or animals.
-
B.
drug delivery device
A drug delivery device is a system or instrument designed to store, control, and administer a specific dose of medication to a patient via a targeted route and schedule.
-
C.
medical technology division
A medical technology division is an organizational unit within a healthcare or life sciences entity responsible for developing, evaluating, and managing medical devices, diagnostic tools, and related technologies to support clinical care and research.
-
D.
Patient Care Device integration profile
The Patient Care Device integration profile defines how medical devices and healthcare information systems communicate and exchange data to ensure accurate, timely, and interoperable patient monitoring and therapy management.
-
E.
portable medical device
A portable medical device is a compact, self-contained piece of medical equipment designed to be easily transported and used in various settings to monitor, diagnose, or treat patients outside traditional clinical environments.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:12 p.m.