Triple
T13505625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephania tetrandra |
E321007
|
entity |
| Predicate | hasBioactivity |
P58407
|
FINISHED |
| Object | antihypertensive potential |
—
|
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: antihypertensive potential | Statement: [Stephania tetrandra, hasBioactivity, antihypertensive potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBioactivity Context triple: [Stephania tetrandra, hasBioactivity, antihypertensive potential]
-
A.
hasBioavailability
Indicates that a substance has a specified degree or measure of bioavailability, i.e., the proportion that enters circulation and can have an active effect.
-
B.
hasDrugBankID
Indicates that an entity is associated with a specific identifier from the DrugBank database.
-
C.
hasPharmacologicalEffect
chosen
Indicates that one entity produces a specific pharmacological effect or action on another entity.
-
D.
hasActiveMetabolite
Indicates that a substance produces one or more metabolites that remain pharmacologically active in the body.
-
E.
hasBiologicalComponents
Indicates that an entity is composed of, contains, or is associated with one or more biological parts or substances.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.