Triple
T13308019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharpless epoxidation |
E316986
|
entity |
| Predicate | stereochemicalOutcome |
P109438
|
FINISHED |
| Object | enantioselective |
—
|
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: enantioselective | Statement: [Sharpless epoxidation, stereochemicalOutcome, enantioselective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stereochemicalOutcome Context triple: [Sharpless epoxidation, stereochemicalOutcome, enantioselective]
-
A.
isEnantiomerOf
Indicates that two molecular entities are non-superimposable mirror images of each other, related by inversion of all chiral centers.
-
B.
hasChiralCenters
Indicates that a molecule possesses one or more chiral (stereogenic) centers, leading to possible stereoisomerism.
-
C.
isomer
Indicates that two chemical species share the same molecular formula but differ in the arrangement or orientation of their atoms, resulting in distinct structures or properties.
-
D.
sideReaction
Indicates that one reaction occurs as an unintended or secondary process alongside a primary reaction.
-
E.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:29 p.m.