Triple
T22516372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | voriconazole |
E556657
|
entity |
| Predicate | hasSpectrumOfActivity |
P99743
|
FINISHED |
| Object | molds |
—
|
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: molds | Statement: [voriconazole, hasSpectrumOfActivity, molds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectrumOfActivity Context triple: [voriconazole, hasSpectrumOfActivity, molds]
-
A.
spectrumOfActivity
chosen
Indicates the range and variety of targets, conditions, or effects over which an action, agent, or process is effective or operative.
-
B.
hasConditionSpectrum
Indicates that an entity is associated with a range or continuum of related conditions rather than a single discrete condition.
-
C.
hasPharmacologicalEffect
Indicates that one entity produces a specific pharmacological effect or action on another entity.
-
D.
hasActiveSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or actively present.
-
E.
hasEnergySpectrum
Indicates that one entity possesses or is characterized by a distribution of energy values (an energy spectrum).
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e2cfc908190b3489228a1997f45 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.