Triple
T73074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 11073 medical device communication standards |
E1463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical device communication standard |
C165
|
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 communication standard Context triple: [IEEE 11073 medical device communication standards, instanceOf, medical device communication standard]
-
A.
IEEE standard
chosen
An IEEE standard is a formally documented set of technical specifications and guidelines developed and maintained by the Institute of Electrical and Electronics Engineers to ensure interoperability, safety, and quality across electrical, electronic, and computing technologies.
-
B.
serial bus interface standard
A serial bus interface standard defines the electrical, timing, and protocol rules that govern how devices communicate and exchange data over a serial communication bus.
-
C.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
D.
computer hardware interface
A computer hardware interface is the physical and logical connection standard that enables communication and data exchange between a computer’s internal components or external devices and the system.
-
E.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
- 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.