Triple
T25360066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evans aldol reaction |
E635933
|
entity |
| Predicate | typicalAuxiliarySubstituent |
P192269
|
FINISHED |
| Object | 4-benzyl group |
—
|
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: 4-benzyl group | Statement: [Evans aldol reaction, typicalAuxiliarySubstituent, 4-benzyl group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAuxiliarySubstituent Context triple: [Evans aldol reaction, typicalAuxiliarySubstituent, 4-benzyl group]
-
A.
typicalCarbeneSubstituents
Indicates that the specified substituents are commonly or characteristically found attached to a carbene center.
-
B.
typicalElectrophile
Indicates that an entity commonly acts as an electrophile, tending to accept electron pairs in chemical reactions.
-
C.
typicalSubunitOf
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
D.
typicalOxidant
Indicates that one entity commonly functions as an oxidizing agent in reactions involving the other entity.
-
E.
secondaryConstituent
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of another entity.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 21, 2026, 1:36 p.m.