Triple
T5114882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rivastigmine |
E115306
|
entity |
| Predicate | isAdministeredWithFood |
P24048
|
FINISHED |
| Object | to improve gastrointestinal tolerability |
—
|
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: to improve gastrointestinal tolerability | Statement: [rivastigmine, isAdministeredWithFood, to improve gastrointestinal tolerability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdministeredWithFood Context triple: [rivastigmine, isAdministeredWithFood, to improve gastrointestinal tolerability]
-
A.
administeredWith
chosen
Indicates that two or more treatments, drugs, or interventions are given to a patient at the same time or as part of the same therapeutic regimen.
-
B.
eatingPermitted
Indicates that an entity is allowed or authorized to eat in a given context or situation.
-
C.
eatenAs
Indicates that one entity is consumed or used as food by another entity.
-
D.
hasStapleFood
Indicates that an entity’s primary or regularly consumed basic food item is another specified entity.
-
E.
mayBeGivenTo
Indicates that something is permitted or eligible to be transferred, assigned, or provided from one entity to 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_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.