Triple
T33840806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbott Diabetes Care |
E867353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical device manufacturer division |
C7926
|
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 manufacturer division Context triple: [Abbott Diabetes Care, instanceOf, medical device manufacturer division]
-
A.
medical technology division
chosen
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.
-
B.
medical device development company
A medical device development company is an organization that researches, designs, tests, and brings to market innovative healthcare technologies and instruments to diagnose, treat, or monitor medical conditions.
-
C.
pharmaceutical division
A pharmaceutical division is an organizational unit within a company responsible for researching, developing, manufacturing, and marketing medicinal products and therapies.
-
D.
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.
-
E.
medical technology institute
A medical technology institute is an organization dedicated to researching, developing, and educating in advanced technologies and devices that improve healthcare diagnosis, treatment, and patient outcomes.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.