Triple
T22717808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegra |
E561779
|
entity |
| Predicate | typicalAdultDoseAllergicRhinitis |
P149431
|
FINISHED |
| Object | 180 mg once daily |
—
|
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: 180 mg once daily | Statement: [Allegra, typicalAdultDoseAllergicRhinitis, 180 mg once daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAdultDoseAllergicRhinitis Context triple: [Allegra, typicalAdultDoseAllergicRhinitis, 180 mg once daily]
-
A.
maximumDailyDoseTypicalAdult
Indicates the highest amount of a substance that a typical adult is recommended or allowed to take in one day.
-
B.
typicalDoseCount
Indicates the usual number of doses administered or taken in a standard course of use.
-
C.
hasCommonStartingDose_mgPerDay
Indicates that two treatments share the same typical initial dosage, measured in milligrams per day.
-
D.
typicalDosageCategories
Indicates the standard dosage ranges or categories typically associated with a given treatment, substance, or medication.
-
E.
typicalDosingFrequency
Indicates how often a treatment or medication is usually administered within a standard dosing regimen.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ecbc48190926d16b20b674dbd |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:19 p.m.