Triple
T27741584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diels–Alder reaction |
E701868
|
entity |
| Predicate | orbitalInteraction |
P164342
|
FINISHED |
| Object | HOMO(diene)–LUMO(dienophile) |
—
|
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: HOMO(diene)–LUMO(dienophile) | Statement: [Diels–Alder reaction, orbitalInteraction, HOMO(diene)–LUMO(dienophile)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalInteraction Context triple: [Diels–Alder reaction, orbitalInteraction, HOMO(diene)–LUMO(dienophile)]
-
A.
orbitalAssociation
Indicates a relationship in which one object is gravitationally bound to and moves in an orbit around another object.
-
B.
isOrbital
Indicates that one entity moves in a curved, repeating path around another entity due to gravitational or similar central forces.
-
C.
hasOrbitalOrder
Indicates that there is a specified sequence or arrangement in which entities occupy or follow orbital positions relative to one another.
-
D.
orbitalComponent
Indicates that one entity is a component or part of another entity’s orbital system or orbital structure.
-
E.
hasOrbitalFunction
Indicates that an entity performs or is associated with a function related to orbiting or orbital operations.
- F. None of above. chosen
Provenance (4 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_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 4:11 p.m.