Triple
T24045456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brown hydroboration |
E595505
|
entity |
| Predicate | followUpTransformation |
P32415
|
FINISHED |
| Object | oxidation to alcohol |
—
|
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: oxidation to alcohol | Statement: [Brown hydroboration, followUpTransformation, oxidation to alcohol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followUpTransformation Context triple: [Brown hydroboration, followUpTransformation, oxidation to alcohol]
-
A.
followUpType
Indicates the specific category or nature of a follow-up action or interaction that occurs after an initial event or communication.
-
B.
followsUp
chosen
Indicates that one entity continues, responds to, or builds upon a previous entity, typically as a subsequent action, communication, or step.
-
C.
followUpMechanism
Indicates a mechanism or process that is used to continue, monitor, or respond to a prior action, event, or communication.
-
D.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
-
E.
followUpDescription
Indicates that one entity provides additional information, clarification, or continuation related to a prior action, event, or communication involving 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9c9391c819095ea6232fa872d5c |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:13 p.m.