Triple
T5114912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memantine |
E115307
|
entity |
| Predicate | maySlow |
P42633
|
FINISHED |
| Object | clinical worsening in moderate to severe Alzheimer’s disease |
—
|
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: clinical worsening in moderate to severe Alzheimer’s disease | Statement: [Memantine, maySlow, clinical worsening in moderate to severe Alzheimer’s disease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySlow Context triple: [Memantine, maySlow, clinical worsening in moderate to severe Alzheimer’s disease]
-
A.
mayDelay
chosen
Indicates that one entity has the potential or permission to cause a postponement or slowing of another entity, event, or process.
-
B.
slowerThan
Indicates that one entity moves or operates at a lower speed than another entity.
-
C.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head of another entity.
-
D.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
E.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ce6044819094166aebf0688665 |
completed | March 20, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.