Triple
T33205651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cytochrome P450 reductase |
E850009
|
entity |
| Predicate | enablesProcess |
P140493
|
FINISHED |
| Object | drug metabolism |
—
|
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: drug metabolism | Statement: [cytochrome P450 reductase, enablesProcess, drug metabolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesProcess Context triple: [cytochrome P450 reductase, enablesProcess, drug metabolism]
-
A.
supportsProcesses
chosen
Indicates that one entity provides the necessary functionality, resources, or environment for certain processes of another entity to operate or be carried out.
-
B.
definesProcessFor
Indicates that one entity specifies or establishes the process or procedure to be used for another entity.
-
C.
regulatesProcess
Indicates that one entity controls, modulates, or influences the occurrence, rate, or outcome of a process involving another entity.
-
D.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
E.
allowsPremiumProcessing
Indicates that one entity permits another entity to use an expedited or premium processing service for a given request or operation.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.