Triple
T16418888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eschenmoser–Claisen rearrangement |
E398759
|
entity |
| Predicate | bondReorganization |
P9392
|
FINISHED |
| Object | [3,3]-sigmatropic shift |
—
|
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: [3,3]-sigmatropic shift | Statement: [Eschenmoser–Claisen rearrangement, bondReorganization, [3,3]-sigmatropic shift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bondReorganization Context triple: [Eschenmoser–Claisen rearrangement, bondReorganization, [3,3]-sigmatropic shift]
-
A.
reorganizedDueTo
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
-
B.
reorganizationAction
Indicates an action that restructures or reorganizes an existing organizational, structural, or functional arrangement.
-
C.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
D.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
E.
isPartOfReorganization
chosen
Indicates that an entity is involved in, or belongs to, a structural or organizational reconfiguration process.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3287a3d348190831b12101d8449b6 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.