Triple
T22717714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aubagio |
E561778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disease-modifying therapy for multiple sclerosis |
C7045
|
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: disease-modifying therapy for multiple sclerosis Context triple: [Aubagio, instanceOf, disease-modifying therapy for multiple sclerosis]
-
A.
disease-modifying therapy
A disease-modifying therapy is a treatment that alters the underlying course or mechanisms of a disease to slow its progression, reduce long-term damage, or change its overall outcome rather than just alleviating symptoms.
-
B.
multiple sclerosis therapy
Multiple sclerosis therapy encompasses medical, rehabilitative, and lifestyle interventions aimed at modifying disease activity, managing symptoms, and preserving function and quality of life in individuals with multiple sclerosis.
-
C.
multiple sclerosis medication
chosen
A multiple sclerosis medication is a drug or therapeutic agent designed to modify the disease course, manage relapses, or alleviate symptoms in individuals with multiple sclerosis by targeting immune or neurological processes.
-
D.
clinical course subtype of multiple sclerosis
A clinical course subtype of multiple sclerosis is a categorization of the disease based on the characteristic pattern of symptom onset, progression, and remission over time.
-
E.
multiple sclerosis advocate
A multiple sclerosis advocate is an individual who actively supports, educates, and campaigns for the rights, resources, and well-being of people living with multiple sclerosis.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:19 p.m.