Triple
T22693648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiglutik |
E561111
|
entity |
| Predicate | containsDosageForm |
P23152
|
FINISHED |
| Object | oral liquid |
—
|
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: oral liquid | Statement: [Tiglutik, containsDosageForm, oral liquid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDosageForm Context triple: [Tiglutik, containsDosageForm, oral liquid]
-
A.
hasDosageForm
chosen
Indicates the specific physical form or presentation in which a drug or medicinal product is supplied or administered (e.g., tablet, injection, cream).
-
B.
hasDoseUnit
Indicates the unit of measurement in which a specified dose or quantity of a substance is expressed.
-
C.
hasCommonDoseStrength
Indicates that two medicinal products share at least one identical dosage strength.
-
D.
dosageStyles
Indicates the various ways or formats in which a dosage (amount and schedule of administration) is specified or presented for a treatment or medication.
-
E.
isExtendedReleaseFormulationOf
Indicates that one pharmaceutical formulation is an extended-release version of another, designed to release the active ingredient more slowly over time.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.