Triple
T13308080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharpless asymmetric dihydroxylation |
E316987
|
entity |
| Predicate | addsFunctionalGroup |
P109440
|
FINISHED |
| Object | hydroxyl group |
—
|
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: hydroxyl group | Statement: [Sharpless asymmetric dihydroxylation, addsFunctionalGroup, hydroxyl group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsFunctionalGroup Context triple: [Sharpless asymmetric dihydroxylation, addsFunctionalGroup, hydroxyl group]
-
A.
hasFunctionalGroup
Indicates that one chemical entity contains or is characterized by a specific functional group as part of its molecular structure.
-
B.
addsGroupActivity
Indicates that an entity performs an action to include or associate a group activity with another entity.
-
C.
mainAddresseeGroup
Indicates that a specified group is the primary intended recipient or audience of a message, communication, or address.
-
D.
groupFunction
Indicates that an entity serves a specific role, purpose, or function within a group or collective context.
-
E.
addsClass
Indicates that one entity introduces or appends a class (such as a classification, type, or code) to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:29 p.m.