Triple
T38297662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shi epoxidation |
E1032134
|
entity |
| Predicate | usesOxidant |
P7195
|
FINISHED |
| Object | oxone |
—
|
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: oxone | Statement: [Shi epoxidation, usesOxidant, oxone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOxidant Context triple: [Shi epoxidation, usesOxidant, oxone]
-
A.
typicalOxidant
Indicates that one entity commonly functions as an oxidizing agent in reactions involving the other entity.
-
B.
oxidizer
chosen
Indicates a relationship where one entity acts as an oxidizing agent that accepts electrons from, or promotes the oxidation of, another entity in a chemical process.
-
C.
oxideProperty
Indicates that a specified property or characteristic pertains to an oxide formed from a given element or compound.
-
D.
oxidizerRich
Indicates that a reaction mixture or combustion process contains a higher proportion of oxidizer than fuel, resulting in oxidizer-rich conditions.
-
E.
oxidizerState
Indicates the physical or chemical state (e.g., solid, liquid, gas, concentration, or phase condition) in which an oxidizing agent exists during a reaction or 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.