Triple
T6003603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taltz |
E133652
|
entity |
| Predicate | hasFirstFDAApprovalYear |
P24562
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Taltz, hasFirstFDAApprovalYear, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstFDAApprovalYear Context triple: [Taltz, hasFirstFDAApprovalYear, 2016]
-
A.
isFirstDrugApprovedFor
Indicates that a drug is the earliest or original medication approved for treating a particular condition, disease, or indication.
-
B.
regulatoryApprovalYear
chosen
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or entity.
-
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.
hasRegulatoryApproval
Indicates that an entity has received formal authorization or clearance from a relevant regulatory authority to operate, be sold, or be used in a specified context.
-
E.
dateOfFirstStatuteApproval
Indicates the date on which a statute (or legal act) was first formally approved.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f0f63148190826198281dce3713 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.