Triple
T4131838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oseltamivir |
E85057
|
entity |
| Predicate | wasWidelyUsedDuring |
P3656
|
FINISHED |
| Object | 2009 H1N1 influenza pandemic |
—
|
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: 2009 H1N1 influenza pandemic | Statement: [oseltamivir, wasWidelyUsedDuring, 2009 H1N1 influenza pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasWidelyUsedDuring Context triple: [oseltamivir, wasWidelyUsedDuring, 2009 H1N1 influenza pandemic]
-
A.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
-
B.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:42 p.m.