Triple
T27741610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diels–Alder reaction |
E701868
|
entity |
| Predicate | electronDemand |
P188770
|
FINISHED |
| Object | normal electron-demand |
—
|
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: normal electron-demand | Statement: [Diels–Alder reaction, electronDemand, normal electron-demand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronDemand Context triple: [Diels–Alder reaction, electronDemand, normal electron-demand]
-
A.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
-
B.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
C.
electronSource
Indicates a relationship where one entity serves as the origin or provider of electrons for another entity or process.
-
D.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
E.
meetsOnDemandOf
Indicates that one entity meets another specifically in response to a request or demand made by that other entity.
- 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_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: April 27, 2026, 4:11 p.m.