Triple
T19992897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namenda |
E494105
|
entity |
| Predicate | canBeAdministeredWithFood |
P68666
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Namenda, canBeAdministeredWithFood, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAdministeredWithFood Context triple: [Namenda, canBeAdministeredWithFood, true]
-
A.
administrationWithFood
chosen
Indicates that a substance (such as a medication) is to be taken together with food or during a meal.
-
B.
nutritionTitleAdministeredBy
Indicates that a specific nutrition-related title, role, or designation is assigned or granted by a particular administering authority or entity.
-
C.
administeredWith
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.
-
D.
laterAdministeredAs
Indicates that something was given or applied at a subsequent time, following an earlier event or condition.
-
E.
administeredAlongside
Indicates that one treatment, drug, or intervention is given or applied at the same time as 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_69e65fe2036c8190b9f313215ad44e87 |
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.