Triple
T19992950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebixa |
E494106
|
entity |
| Predicate | maximumDailyDose |
P37216
|
FINISHED |
| Object | 20 mg memantine (typical in adults) |
—
|
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: 20 mg memantine (typical in adults) | Statement: [Ebixa, maximumDailyDose, 20 mg memantine (typical in adults)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDailyDose Context triple: [Ebixa, maximumDailyDose, 20 mg memantine (typical in adults)]
-
A.
maximumDailyDoseTypicalAdult
chosen
Indicates the highest amount of a substance that a typical adult is recommended or allowed to take in one day.
-
B.
hasDefinedDailyDose
Indicates that an entity has an established standard amount intended to be taken or used per day.
-
C.
hasCommonStartingDose_mgPerDay
Indicates that two treatments share the same typical initial dosage, measured in milligrams per day.
-
D.
dosageLevel
Indicates the specific amount or intensity of a substance or treatment administered in a given dose.
-
E.
hasHigherDoseStrength
Indicates that one entity has a greater dose strength than another entity in a comparative relationship.
- 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.