Triple
T33291711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pgp |
E852336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ATP-dependent efflux pump |
C27655
|
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: ATP-dependent efflux pump Context triple: [Pgp, instanceOf, ATP-dependent efflux pump]
-
A.
ATP-dependent efflux transporter protein
chosen
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.
-
B.
efflux transporter
An efflux transporter is a membrane protein that actively exports specific substrates, such as drugs, toxins, or metabolites, out of cells to regulate intracellular concentrations and protect against harmful compounds.
-
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.
multidrug resistance protein
A multidrug resistance protein is a membrane transporter that actively exports a wide range of structurally diverse drugs and toxins out of cells, thereby reducing their intracellular concentrations and contributing to drug resistance.
-
E.
drug transporter
A drug transporter is a membrane protein that facilitates the movement of pharmaceutical compounds across cellular barriers, influencing their absorption, distribution, and elimination in the body.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.