Triple
T13308103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharpless asymmetric dihydroxylation |
E316987
|
entity |
| Predicate | worksBestOn |
P2367
|
FINISHED |
| Object | terminal alkenes |
—
|
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: terminal alkenes | Statement: [Sharpless asymmetric dihydroxylation, worksBestOn, terminal alkenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksBestOn Context triple: [Sharpless asymmetric dihydroxylation, worksBestOn, terminal alkenes]
-
A.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
B.
worksWhen
Indicates that one entity functions or operates correctly only under the conditions or context defined by another entity.
-
C.
worksThrough
Indicates that one entity performs an action, causes an effect, or achieves a result by using, employing, or acting via another entity as an intermediary or means.
-
D.
usedOn
chosen
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
E.
worksAs
Indicates that an entity performs the role, job, or occupation specified by 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.