Triple
T27211056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stork enamine reaction |
E683997
|
entity |
| Predicate | hasNucleophile |
P181041
|
FINISHED |
| Object | enamine |
—
|
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: enamine | Statement: [Stork enamine reaction, hasNucleophile, enamine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNucleophile Context triple: [Stork enamine reaction, hasNucleophile, enamine]
-
A.
hasElectrophile
Indicates that an entity possesses or is associated with an electrophilic group or species capable of accepting electrons in a chemical reaction.
-
B.
nucleophileType
Indicates the classification of a species based on the type or character of its nucleophilic behavior in a chemical reaction.
-
C.
usesHydrogenAtomDonor
Indicates that one entity employs another entity as a source of hydrogen atoms (a hydrogen donor) in a chemical or biochemical process.
-
D.
hasAnion
Indicates that one entity possesses, contains, or is associated with another entity functioning as its anion (negatively charged ion).
-
E.
hasConjugateBase
Indicates that one chemical species is the conjugate base formed when another species donates a proton (H⁺).
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 27, 2026, 9:39 a.m.