Triple
T32195979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | phenytoin |
E822404
|
entity |
| Predicate | wasIntroducedAsAnticonvulsantIn |
P173308
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [phenytoin, wasIntroducedAsAnticonvulsantIn, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIntroducedAsAnticonvulsantIn Context triple: [phenytoin, wasIntroducedAsAnticonvulsantIn, 1938]
-
A.
isFirstDrugApprovedFor
Indicates that a drug is the earliest or original medication approved for treating a particular condition, disease, or indication.
-
B.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
-
C.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
D.
introducedAsFirst
Indicates that one entity is presented or mentioned before any others in a given context or sequence.
-
E.
introducedUse
Indicates that one entity initiated or brought another entity into use, practice, or operation.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb3795fc8190bfcb00d45aa887a1 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:35 a.m.