Triple
T25360063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evans aldol reaction |
E635933
|
entity |
| Predicate | hasStereocontrolOrigin |
P153225
|
FINISHED |
| Object | chiral auxiliary |
—
|
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: chiral auxiliary | Statement: [Evans aldol reaction, hasStereocontrolOrigin, chiral auxiliary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStereocontrolOrigin Context triple: [Evans aldol reaction, hasStereocontrolOrigin, chiral auxiliary]
-
A.
hasStereoOutput
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
B.
stereocontrolElement
chosen
Indicates a relationship where one element controls or influences the stereochemical outcome or configuration of another in a molecular or structural context.
-
C.
stereoCapability
Indicates that an entity has the ability to produce, process, or support stereo (two-channel) audio.
-
D.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
-
E.
canAcquireStereoPairs
Indicates that an entity is capable of obtaining or generating stereo image pairs suitable for stereoscopic or depth-related processing.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 1:36 p.m.