Triple
T11115614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepcid |
E262876
|
entity |
| Predicate | hasPrescriptionStrength |
P97024
|
FINISHED |
| Object | 20 mg famotidine tablet |
—
|
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 famotidine tablet | Statement: [Pepcid, hasPrescriptionStrength, 20 mg famotidine tablet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrescriptionStrength Context triple: [Pepcid, hasPrescriptionStrength, 20 mg famotidine tablet]
-
A.
hasHigherDoseStrength
Indicates that one entity has a greater dose strength than another entity in a comparative relationship.
-
B.
isPrescriptionOnly
Indicates that the item can only be obtained or used when authorized by a licensed prescriber, such as through a formal prescription.
-
C.
hasDefinedDailyDose
Indicates that an entity has an established standard amount intended to be taken or used per day.
-
D.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
E.
prescribedBy
Indicates that something (typically a treatment, medication, or procedure) has been formally ordered or authorized by a specific agent, usually a medical professional.
- F. None of above. chosen
Provenance (4 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa7254c8190abce35696ad2be03 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750cb26f48190a134614d0aa8e283 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.