Triple
T38297694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shi epoxidation |
E1032134
|
entity |
| Predicate | stereocontrolSource |
P153225
|
FINISHED |
| Object | chiral ketone catalyst |
—
|
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: chiral ketone catalyst | Statement: [Shi epoxidation, stereocontrolSource, chiral ketone catalyst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stereocontrolSource Context triple: [Shi epoxidation, stereocontrolSource, chiral ketone catalyst]
-
A.
stereocontrolElement
chosen
Indicates a relationship where one element controls or influences the stereochemical outcome or configuration of another in a molecular or structural context.
-
B.
stereoConfiguration
Indicates how multiple audio channels are arranged and related to each other in a stereo sound setup.
-
C.
stereoCapability
Indicates that an entity has the ability to produce, process, or support stereo (two-channel) audio.
-
D.
hasStereoOutput
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
E.
supportsVolumeControl
Indicates that one entity provides the capability to adjust or manage the audio volume level of another entity.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.