Triple
T9855020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persona Knee System |
E239561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | orthopedic medical device |
C6456
|
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: orthopedic medical device Context triple: [Persona Knee System, instanceOf, orthopedic medical device]
-
A.
medical device
chosen
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.
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.
-
C.
medical device regulation system
A medical device regulation system is a framework of processes, rules, and oversight mechanisms that govern the evaluation, approval, monitoring, and post-market surveillance of medical devices to ensure their safety, effectiveness, and compliance with regulatory standards.
-
D.
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.
-
E.
advanced prosthetic limb
An advanced prosthetic limb is a highly engineered artificial appendage that integrates sensors, actuators, and adaptive control systems to closely mimic the movement, function, and sometimes sensory feedback of a natural human limb.
- 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_69ca84e4fdc08190a624425bcef98665 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:34 p.m.