Triple
T28374700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dihydroartemisinin |
E718725
|
entity |
| Predicate | hasChEBIID |
P180708
|
FINISHED |
| Object | CHEBI:94685 |
—
|
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: CHEBI:94685 | Statement: [dihydroartemisinin, hasChEBIID, CHEBI:94685]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChEBIID Context triple: [dihydroartemisinin, hasChEBIID, CHEBI:94685]
-
A.
hasChEMBLID
Indicates that an entity is associated with a specific ChEMBL database identifier that uniquely references it in the ChEMBL bioactivity resource.
-
B.
hasPubChemCID
Indicates that an entity (typically a chemical substance) is associated with a specific PubChem Compound Identifier (CID) in the PubChem database.
-
C.
hasEnzymeCommissionNumber
Indicates that an entity is associated with a specific Enzyme Commission (EC) number that classifies its enzymatic activity.
-
D.
hasDrugBankID
Indicates that an entity is associated with a specific identifier from the DrugBank database.
-
E.
hasChiralCenters
Indicates that a molecule possesses one or more chiral (stereogenic) centers, leading to possible stereoisomerism.
- F. None of above. chosen
Provenance (4 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
| PDg | Predicate description generation | batch_69f74c6fa6548190b03935f65429a24e |
completed | May 3, 2026, 1:23 p.m. |
Created at: April 28, 2026, 1:02 a.m.