Triple
T38297671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shi epoxidation |
E1032134
|
entity |
| Predicate | catalystOrigin |
P137413
|
FINISHED |
| Object | carbohydrate-derived ketone |
—
|
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: carbohydrate-derived ketone | Statement: [Shi epoxidation, catalystOrigin, carbohydrate-derived ketone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalystOrigin Context triple: [Shi epoxidation, catalystOrigin, carbohydrate-derived ketone]
-
A.
causeOfOrigin
Indicates that one entity is the source or initiating cause from which another entity originates or comes into existence.
-
B.
describesOriginOf
chosen
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
-
C.
coreStageOrigin
Indicates the location or source from which the core stage of an object or process originates.
-
D.
originBloc
Indicates that one entity originates from, or has its source in, a particular bloc, group, or geopolitical alliance.
-
E.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
- 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_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.