Triple
T24045509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydroboration |
E595506
|
entity |
| Predicate | coversReactionType |
P69657
|
FINISHED |
| Object | addition reactions |
—
|
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: addition reactions | Statement: [Hydroboration, coversReactionType, addition reactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversReactionType Context triple: [Hydroboration, coversReactionType, addition reactions]
-
A.
relatedReaction
Indicates that one reaction is connected or associated with another reaction in some relevant way.
-
B.
containsReaction
Indicates that one entity includes or encompasses a specific reaction as part of its contents or structure.
-
C.
reactionType
chosen
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
D.
coversActionType
Indicates that one entity’s scope, responsibility, or applicability includes or encompasses a particular type of action.
-
E.
featuresReaction
Indicates that one entity exhibits, displays, or includes a particular reaction associated with another entity or context.
- 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:14 p.m.