Triple
T22067587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson annulation reaction |
E545316
|
entity |
| Predicate | typicalNucleophile |
P124695
|
FINISHED |
| Object | enolate |
—
|
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 | Statement: [Robinson annulation reaction, typicalNucleophile, enolate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNucleophile Context triple: [Robinson annulation reaction, typicalNucleophile, enolate]
-
A.
nucleophileType
chosen
Indicates the classification of a species based on the type or character of its nucleophilic behavior in a chemical reaction.
-
B.
isTypicallyNeutralizedWith
Indicates that something is commonly counteracted, rendered harmless, or balanced by another specified thing.
-
C.
typicalOxidant
Indicates that one entity commonly functions as an oxidizing agent in reactions involving the other entity.
-
D.
typicalSolvent
Indicates that one entity is commonly or characteristically used as a solvent for the other entity.
-
E.
typicalProtein
Indicates that one entity is a representative or characteristic example of a particular protein type or class.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12884937c819095d3af69123fa2cb |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.