Triple
T20125690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fentanyl |
E490748
|
entity |
| Predicate | primaryMedicalUse |
P40313
|
FINISHED |
| Object | treatment of severe pain |
—
|
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: treatment of severe pain | Statement: [Fentanyl, primaryMedicalUse, treatment of severe pain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMedicalUse Context triple: [Fentanyl, primaryMedicalUse, treatment of severe pain]
-
A.
medicinalUse
chosen
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
B.
primaryDrug
Indicates that one drug is identified as the main or most important medication in a given treatment, context, or combination relative to other associated drugs.
-
C.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
D.
primaryHumanUse
Indicates the main way humans typically use, interact with, or benefit from the referenced entity.
-
E.
potentialTherapeuticUse
Indicates that something is being considered or investigated as a possible treatment or therapy for a condition or disease.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6674223008190827c454fe7ac86f4 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.