Triple
T25360082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evans aldol reaction |
E635933
|
entity |
| Predicate | hasMechanisticStep |
P9959
|
FINISHED |
| Object | enolate formation |
—
|
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: enolate formation | Statement: [Evans aldol reaction, hasMechanisticStep, enolate formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMechanisticStep Context triple: [Evans aldol reaction, hasMechanisticStep, enolate formation]
-
A.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasStep
chosen
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
C.
hasMechanicalFeature
Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
-
D.
haveHighLevelMechanism
Indicates that an entity possesses or is associated with a high-level, abstract mechanism explaining how something works or occurs.
-
E.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 1:36 p.m.