Triple
T17262100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biota Holdings |
E419031
|
entity |
| Predicate | drugClassDeveloped |
P24605
|
FINISHED |
| Object | neuraminidase inhibitors |
—
|
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: neuraminidase inhibitors | Statement: [Biota Holdings, drugClassDeveloped, neuraminidase inhibitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drugClassDeveloped Context triple: [Biota Holdings, drugClassDeveloped, neuraminidase inhibitors]
-
A.
developedDrugFor
Indicates that one entity created or formulated a drug intended to treat or address a medical condition associated with another entity.
-
B.
drugClass
chosen
Indicates that one entity is classified as a particular pharmacological or therapeutic category of drugs in relation to another entity.
-
C.
hasPharmacologicClass
Indicates that a drug or medicinal product belongs to a specific pharmacologic class based on its mechanism of action or therapeutic effect.
-
D.
coDeveloperDrug
Indicates a relationship where two or more entities jointly participate in the development of a drug.
-
E.
drugProduced
Indicates that a particular drug is manufactured or generated by a specified producer or source.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e717a348190ae6835fb08f38125 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.