Triple
T19066329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corey–Kim oxidation |
E466667
|
entity |
| Predicate | reactionCondition |
P134151
|
FINISHED |
| Object | mild conditions |
—
|
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: mild conditions | Statement: [Corey–Kim oxidation, reactionCondition, mild conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionCondition Context triple: [Corey–Kim oxidation, reactionCondition, mild conditions]
-
A.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
B.
reactionDescription
Indicates a textual explanation or summary of what happens during a reaction, such as its process, outcome, or notable characteristics.
-
C.
ringReaction
Indicates that one entity performs or undergoes a reaction involving a chemical ring structure in relation to another entity.
-
D.
sideReaction
Indicates that one reaction occurs as an unintended or secondary process alongside a primary reaction.
-
E.
reactant
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e198621481908618f65dd01746fc |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:03 p.m.