Triple
T19066296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corey–Bakshi–Shibata reduction |
E466666
|
entity |
| Predicate | substrateScope |
P87256
|
FINISHED |
| Object | aryl alkyl ketones |
—
|
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: aryl alkyl ketones | Statement: [Corey–Bakshi–Shibata reduction, substrateScope, aryl alkyl ketones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: substrateScope Context triple: [Corey–Bakshi–Shibata reduction, substrateScope, aryl alkyl ketones]
-
A.
substrateRelationship
chosen
Indicates that one entity serves as a substrate upon which another entity acts, is processed, or depends in a functional relationship.
-
B.
scopeOfReference
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
C.
laterScope
Indicates that one event, state, or condition occurs or applies after the temporal scope of another.
-
D.
definesScopeFor
Indicates that one entity establishes or delimits the scope, boundaries, or applicability within which another entity operates or is interpreted.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_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. |
Created at: April 10, 2026, 12:03 p.m.