Triple
T38297696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shi epoxidation |
E1032134
|
entity |
| Predicate | catalystClass |
P191420
|
FINISHED |
| Object | chiral dioxirane precursor |
—
|
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: chiral dioxirane precursor | Statement: [Shi epoxidation, catalystClass, chiral dioxirane precursor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalystClass Context triple: [Shi epoxidation, catalystClass, chiral dioxirane precursor]
-
A.
substrateClass
Indicates that one entity serves as the material or medium on which another entity acts, grows, or is processed.
-
B.
designatedClass
Indicates that one entity is formally assigned or specified as the class or category to which another entity belongs.
-
C.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
D.
configurationClass
Indicates that one entity serves as the configuration class (i.e., a class defining configuration settings or parameters) for another entity.
-
E.
operatorClass
Indicates the classification or category of an operator in terms of its type, role, or functional group within a system or domain.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:30 p.m.