Triple
T16803388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trost asymmetric allylic alkylation |
E408414
|
entity |
| Predicate | selectivityType |
P74335
|
FINISHED |
| Object | enantioselectivity |
—
|
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: enantioselectivity | Statement: [Trost asymmetric allylic alkylation, selectivityType, enantioselectivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectivityType Context triple: [Trost asymmetric allylic alkylation, selectivityType, enantioselectivity]
-
A.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
B.
typeOfSelection
chosen
Indicates the specific kind or category of selection being made in a given context.
-
C.
selectionCharacteristic
Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
-
D.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
E.
usedToSelect
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2ca46f88190b56e81d75012496c |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.