Triple
T17483229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephedraceae |
E425714
|
entity |
| Predicate | pharmacologicalProperty |
P58407
|
FINISHED |
| Object | sympathomimetic |
—
|
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: sympathomimetic | Statement: [Ephedraceae, pharmacologicalProperty, sympathomimetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pharmacologicalProperty Context triple: [Ephedraceae, pharmacologicalProperty, sympathomimetic]
-
A.
hasPharmacologicalEffect
chosen
Indicates that one entity produces a specific pharmacological effect or action on another entity.
-
B.
targetSubstanceProperty
Indicates that a particular property or characteristic is being ascribed to, measured for, or associated with a specified target substance.
-
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.
hasChemicalProperty
Indicates that an entity possesses or exhibits a specific chemical property or characteristic.
-
E.
hasDrugBankID
Indicates that an entity is associated with a specific identifier from the DrugBank database.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.