Triple
T33206085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | constitutive androstane receptor |
E850016
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ligand-activated transcription factor |
C46696
|
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: ligand-activated transcription factor Context triple: [constitutive androstane receptor, instanceOf, ligand-activated transcription factor]
-
A.
gene regulatory protein
chosen
A gene regulatory protein is a molecule, typically a transcription factor, that binds specific DNA sequences or associated factors to control the timing, location, and level of gene expression.
-
B.
DNA-binding protein
A DNA-binding protein is a molecule that specifically recognizes and attaches to DNA sequences to regulate or facilitate processes such as transcription, replication, repair, and chromatin organization.
-
C.
G protein–coupled receptor
A G protein–coupled receptor is a membrane-spanning protein that detects extracellular signals and activates intracellular G proteins to trigger specific cellular responses.
-
D.
heterotrimeric G protein
A heterotrimeric G protein is a membrane-associated signaling protein complex composed of three distinct subunits (α, β, and γ) that transduces signals from activated G protein–coupled receptors to intracellular effector pathways by cycling between GDP-bound inactive and GTP-bound active states.
-
E.
GIP receptor agonist
A GIP receptor agonist is a compound that binds to and activates the glucose-dependent insulinotropic polypeptide (GIP) receptor, enhancing insulin secretion and improving glucose regulation.
- 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.