Triple
T27211057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stork enamine reaction |
E683997
|
entity |
| Predicate | hasElectrophile |
P165880
|
FINISHED |
| Object | alkyl halide |
—
|
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: alkyl halide | Statement: [Stork enamine reaction, hasElectrophile, alkyl halide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectrophile Context triple: [Stork enamine reaction, hasElectrophile, alkyl halide]
-
A.
typicalElectrophile
Indicates that an entity commonly acts as an electrophile, tending to accept electron pairs in chemical reactions.
-
B.
hasElectrodeReaction
Indicates that an electrochemical system or component undergoes a specific chemical reaction at one of its electrodes.
-
C.
hasElectronPair
Indicates that one entity possesses a specific pair of electrons associated with or shared in a chemical context with another entity.
-
D.
hasAnion
Indicates that one entity possesses, contains, or is associated with another entity functioning as its anion (negatively charged ion).
-
E.
nucleophileType
Indicates the classification of a species based on the type or character of its nucleophilic behavior in a chemical reaction.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 27, 2026, 9:39 a.m.