Triple
T20125687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fentanyl |
E490748
|
entity |
| Predicate | introducedMedicallyIn |
P8259
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Fentanyl, introducedMedicallyIn, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedMedicallyIn Context triple: [Fentanyl, introducedMedicallyIn, 1960s]
-
A.
isFirstDrugApprovedFor
Indicates that a drug is the earliest or original medication approved for treating a particular condition, disease, or indication.
-
B.
medicinalUse
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
C.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
D.
firstTestedBy
Indicates that an item, concept, or process was initially tested or tried out by a particular agent or entity.
-
E.
wasPioneeredInSurgeryBy
Indicates that a particular surgical technique, procedure, or approach was first developed, introduced, or trailblazed by a specific surgeon or surgical team.
- 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.