Triple
T27660167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venclexta |
E697099
|
entity |
| Predicate | chemicalStructureType |
P38028
|
FINISHED |
| Object | small organic molecule |
—
|
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: small organic molecule | Statement: [Venclexta, chemicalStructureType, small organic molecule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chemicalStructureType Context triple: [Venclexta, chemicalStructureType, small organic molecule]
-
A.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
B.
chemicalForm
Indicates the specific chemical composition or structural variant that characterizes a substance in a given context.
-
C.
hasChemicalClass
chosen
Indicates that an entity belongs to, or is categorized under, a particular chemical class based on its structural or compositional characteristics.
-
D.
hasChemicalFormula
Indicates that one entity (typically a chemical substance) is characterized by or associated with a specific chemical formula representing its elemental composition.
-
E.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f634a016b08190973fd3a552a9757c |
completed | May 2, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:36 p.m.