Triple
T33388511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pomalidomide |
E854983
|
entity |
| Predicate | hasEMAAuthorizationYear |
P7919
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [pomalidomide, hasEMAAuthorizationYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEMAAuthorizationYear Context triple: [pomalidomide, hasEMAAuthorizationYear, 2013]
-
A.
authorizationYear
chosen
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
B.
hasAssociatedYear
Indicates that an entity is linked to a specific year that is relevant to it (e.g., creation, occurrence, or reference year).
-
C.
hasYearType
Indicates a relationship where an entity is associated with a specific classification or category of year (such as calendar, fiscal, academic, or other year type).
-
D.
hasOverrulingYear
Indicates the year in which a prior decision, rule, or action was formally overruled or invalidated.
-
E.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:35 a.m.