Triple
T33206086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | constitutive androstane receptor |
E850016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | xenobiotic sensor |
C58229
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: xenobiotic sensor Context triple: [constitutive androstane receptor, instanceOf, xenobiotic sensor]
-
A.
xenobiotic sensor
chosen
A xenobiotic sensor is a biological or engineered system that detects and responds to foreign chemical substances not naturally produced or expected to be present in an organism.
-
B.
xenobiotic transporter
A xenobiotic transporter is a membrane protein that mediates the uptake, efflux, or intracellular trafficking of foreign chemical substances (xenobiotics), thereby influencing their absorption, distribution, metabolism, and excretion in an organism.
-
C.
cytochrome P450 enzyme
A cytochrome P450 enzyme is a heme-containing monooxygenase that catalyzes the oxidation of a wide variety of endogenous and exogenous substrates, playing key roles in metabolism, detoxification, and biosynthesis.
-
D.
drug-metabolizing enzyme
A drug-metabolizing enzyme is a biological catalyst, typically found in the liver and other tissues, that chemically modifies pharmaceutical compounds to facilitate their activation, inactivation, or elimination from the body.
-
E.
BCRP inhibitor
A BCRP inhibitor is a compound that reduces or blocks the activity of the Breast Cancer Resistance Protein (ABCG2) efflux transporter, thereby altering the absorption, distribution, and elimination of its substrate drugs.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 1:30 a.m.