Triple
T18784258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notch |
E459333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | single-pass transmembrane protein |
C29138
|
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: single-pass transmembrane protein Context triple: [Notch, instanceOf, single-pass transmembrane protein]
-
A.
transmembrane receptor
chosen
A transmembrane receptor is a membrane-spanning protein that detects extracellular signals and transduces them into specific intracellular responses.
-
B.
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.
-
C.
ATP-binding cassette transporter
An ATP-binding cassette transporter is a membrane protein that uses the energy from ATP hydrolysis to move various molecules across cellular membranes, often against their concentration gradients.
-
D.
ATP-dependent efflux transporter protein
An ATP-dependent efflux transporter protein is a membrane-bound protein that uses the energy from ATP hydrolysis to pump specific substrates out of the cell or organelle, thereby regulating intracellular concentrations and contributing to processes such as detoxification, drug resistance, and homeostasis.
-
E.
protein
A protein is a large, complex biological molecule composed of one or more chains of amino acids that fold into specific three-dimensional structures to perform diverse structural, catalytic, signaling, and regulatory functions in living organisms.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.