Triple
T16279309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barton–McCombie deoxygenation |
E395221
|
entity |
| Predicate | transformsFunctionalGroup |
P56260
|
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: [Barton–McCombie deoxygenation, transformsFunctionalGroup, hydroxyl group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformsFunctionalGroup Context triple: [Barton–McCombie deoxygenation, transformsFunctionalGroup, hydroxyl group]
-
A.
transformsUnder
Indicates a relationship where one entity changes form, state, or structure when subjected to the influence, conditions, or operation specified by another entity.
-
B.
transformType
chosen
Indicates that one entity is converted or changed from its original form into another specified type or form.
-
C.
addsFunctionalGroup
Indicates that one entity introduces or attaches a specific functional group to another entity.
-
D.
hasFunctionalGroup
Indicates that one chemical entity contains or is characterized by a specific functional group as part of its molecular structure.
-
E.
transferFunction
Indicates a relationship where some quantity, property, or information is passed or conveyed from one entity to another.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24610908c8190921e507dcb4d8250 |
completed | April 17, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.