Triple
T15739973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Podophyllum |
E381574
|
entity |
| Predicate | pharmaceuticalDerivative |
P23150
|
FINISHED |
| Object | etoposide precursor |
—
|
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: etoposide precursor | Statement: [Podophyllum, pharmaceuticalDerivative, etoposide precursor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pharmaceuticalDerivative Context triple: [Podophyllum, pharmaceuticalDerivative, etoposide precursor]
-
A.
isProdrugOf
chosen
Indicates that one substance is a precursor form that is metabolized in the body to produce the active form of another substance.
-
B.
drugProduced
Indicates that a particular drug is manufactured or generated by a specified producer or source.
-
C.
coDeveloperDrug
Indicates a relationship where two or more entities jointly participate in the development of a drug.
-
D.
developedDrugFor
Indicates that one entity created or formulated a drug intended to treat or address a medical condition associated with another entity.
-
E.
isExtendedReleaseFormulationOf
Indicates that one pharmaceutical formulation is an extended-release version of another, designed to release the active ingredient more slowly over time.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.