Triple

T34091755
Position Surface form Disambiguated ID Type / Status
Subject M2 muscarinic acetylcholine receptor E874316 entity
Predicate instanceOf P0 FINISHED
Object seven-transmembrane receptor C11019 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: seven-transmembrane receptor
Context triple: [M2 muscarinic acetylcholine receptor, instanceOf, seven-transmembrane receptor]
  • A. transmembrane receptor
    A transmembrane receptor is a membrane-spanning protein that detects extracellular signals and transduces them into specific intracellular responses.
  • B. G protein–coupled receptor chosen
    A G protein–coupled receptor is a membrane-spanning protein that detects extracellular signals and activates intracellular G proteins to trigger specific cellular responses.
  • C. 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.
  • D. receptor tyrosine kinase
    A receptor tyrosine kinase is a transmembrane protein that, upon binding an extracellular ligand, dimerizes and autophosphorylates its intracellular tyrosine residues to initiate intracellular signaling cascades regulating cell growth, differentiation, and survival.
  • E. cannabinoid receptor
    A cannabinoid receptor is a cell-surface G protein–coupled receptor that binds endogenous, plant-derived, or synthetic cannabinoids to modulate processes such as pain perception, appetite, mood, and immune function.
  • 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_69f349a735208190a1dbfb1c2a121059 completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 1:52 a.m.