Triple
T19992756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exelon Patch |
E494103
|
entity |
| Predicate | improvesSymptom |
P112879
|
FINISHED |
| Object | cognitive function |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: cognitive function | Statement: [Exelon Patch, improvesSymptom, cognitive function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: improvesSymptom Context triple: [Exelon Patch, improvesSymptom, cognitive function]
-
A.
symptom
Indicates that a particular condition, disease, or problem manifests through a specific observable sign or complaint.
-
B.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
C.
isUsedForSymptom
chosen
Indicates that something (such as a treatment, medication, or intervention) is employed to address, alleviate, or manage a particular symptom.
-
D.
hasImproved
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
E.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
- F. None of above.
Provenance (3 batches)
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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe10ffc81908c94168b0a8ea9c9 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.