Triple
T27741612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diels–Alder reaction |
E701868
|
entity |
| Predicate | isReversibleAt |
P10794
|
FINISHED |
| Object | high temperature |
—
|
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: high temperature | Statement: [Diels–Alder reaction, isReversibleAt, high temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReversibleAt Context triple: [Diels–Alder reaction, isReversibleAt, high temperature]
-
A.
canRevertTo
Indicates that one state, version, or condition has the ability to be changed back or restored to another prior state, version, or condition.
-
B.
reversible
chosen
Indicates that the relationship or process can proceed in both directions, allowing a return to the original state or configuration.
-
C.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
-
D.
hasReverse
Indicates that one entity serves as the inverse or opposite counterpart of another entity in a given relationship or operation.
-
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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637169d6c8190bf74d5b882d2eb7d |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:11 p.m.