Triple
T22690444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | larotrectinib |
E561035
|
entity |
| Predicate | firstFDAApprovalDate |
P24562
|
FINISHED |
| Object | 2018-11 |
—
|
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: 2018-11 | Statement: [larotrectinib, firstFDAApprovalDate, 2018-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFDAApprovalDate Context triple: [larotrectinib, firstFDAApprovalDate, 2018-11]
-
A.
regulatoryApprovalYear
chosen
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or entity.
-
B.
isFirstDrugApprovedFor
Indicates that a drug is the earliest or original medication approved for treating a particular condition, disease, or indication.
-
C.
FDAApprovalType
Indicates the specific regulatory pathway or category under which a product has been approved by the U.S. Food and Drug Administration.
-
D.
USFDAEUAInitialDate
Indicates the date on which the U.S. FDA first granted Emergency Use Authorization (EUA) for the associated product or intervention.
-
E.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
- 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_69f1789a1fd08190bce5fa0babe695d3 |
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.