Triple
T11115505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zyrtec |
E262874
|
entity |
| Predicate | typicalAdultDose |
P37228
|
FINISHED |
| Object | 10 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: 10 mg once daily | Statement: [Zyrtec, typicalAdultDose, 10 mg once daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAdultDose Context triple: [Zyrtec, typicalAdultDose, 10 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.
typicalDosageCategories
Indicates the standard dosage ranges or categories typically associated with a given treatment, substance, or medication.
-
C.
hasMaintenanceDose
Indicates that an entity is associated with a specific ongoing dose used to maintain a desired therapeutic effect after initial treatment.
-
D.
doseRegimen
chosen
Indicates the specific schedule, frequency, and amount with which a dose of a substance or medication is to be administered.
-
E.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
- 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_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. |
Created at: April 8, 2026, 9:27 p.m.