Triple
T27211077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stork enamine reaction |
E683997
|
entity |
| Predicate | typicalEnamineSource |
P200602
|
FINISHED |
| Object | secondary amine |
—
|
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: secondary amine | Statement: [Stork enamine reaction, typicalEnamineSource, secondary amine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnamineSource Context triple: [Stork enamine reaction, typicalEnamineSource, secondary amine]
-
A.
chemicallyRelatedTo
Indicates a relationship where two entities are connected through a chemical association, such as sharing structural features, participating in related reactions, or being derivable from one another chemically.
-
B.
chemicalSeries
Indicates that one chemical entity belongs to, or is part of, a defined series of related chemical compounds.
-
C.
keyChemicalDiscussed
Indicates that a particular chemical substance is a central topic of discussion in a given context or communication.
-
D.
commonChiralSource
Indicates that two entities share the same origin or cause for their chirality.
-
E.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
| PDg | Predicate description generation | batch_69ff9b19f254819099bb9c034d2b399b |
completed | May 9, 2026, 8:37 p.m. |
Created at: April 27, 2026, 9:39 a.m.