Triple
T27599303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exponential Medicine |
E699992
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical innovation conference |
C6882
|
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 innovation conference Context triple: [Exponential Medicine, instanceOf, medical innovation conference]
-
A.
health conference
chosen
A health conference is a structured event where healthcare professionals, researchers, policymakers, and stakeholders gather to share knowledge, discuss current issues, and explore innovations in health and medicine.
-
B.
healthcare innovation hub
A healthcare innovation hub is a collaborative ecosystem that brings together clinicians, researchers, entrepreneurs, and technologists to develop, test, and scale new solutions that improve health outcomes, patient experience, and system efficiency.
-
C.
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.
-
D.
innovation summit
An innovation summit is a collaborative event where leaders, experts, and stakeholders gather to share ideas, showcase emerging technologies, and develop strategies that drive forward-thinking solutions and transformative change.
-
E.
medical technology
Medical technology encompasses the tools, devices, software, and procedures used to prevent, diagnose, monitor, and treat health conditions, improving patient outcomes and healthcare delivery.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:07 p.m.