Triple
T4200586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | zanamivir |
E86054
|
entity |
| Predicate | effectiveAgainst |
P13821
|
FINISHED |
| Object | 2009 H1N1 influenza A virus |
—
|
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 A virus | Statement: [zanamivir, effectiveAgainst, 2009 H1N1 influenza A virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveAgainst Context triple: [zanamivir, effectiveAgainst, 2009 H1N1 influenza A virus]
-
A.
usedAgainst
chosen
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
B.
competitiveEffect
Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
-
C.
wirksamAb
Indicates the point in time from which something (such as a rule, contract, or condition) becomes effective or valid.
-
D.
designedToDefeat
Indicates that one entity is intentionally created or configured with the purpose of overcoming, neutralizing, or rendering ineffective another entity.
-
E.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0363bbb8819093f396afe91972e2 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.