Triple
T7803639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fischer esterification |
E180491
|
entity |
| Predicate | reverseReaction |
P9300
|
FINISHED |
| Object | acid-catalyzed ester hydrolysis |
—
|
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: acid-catalyzed ester hydrolysis | Statement: [Fischer esterification, reverseReaction, acid-catalyzed ester hydrolysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseReaction Context triple: [Fischer esterification, reverseReaction, acid-catalyzed ester hydrolysis]
-
A.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
B.
reversed
chosen
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
C.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
D.
reversible
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
E.
reversibility
Indicates that a process, action, or transformation can be undone or reversed to restore the original state or conditions.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:34 p.m.