Triple
T36599925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD21 |
E902889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | immune system protein |
C19743
|
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: immune system protein Context triple: [CD21, instanceOf, immune system protein]
-
A.
protein
chosen
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.
-
B.
interleukin
An interleukin is a type of cytokine protein produced mainly by leukocytes that mediates communication between immune cells to regulate inflammation, immune responses, and cell development.
-
C.
immune checkpoint ligand
An immune checkpoint ligand is a molecule, typically expressed on the surface of cells, that binds to corresponding immune checkpoint receptors to modulate and often inhibit immune cell activation and maintain immune homeostasis.
-
D.
innate immune signaling pathway
The innate immune signaling pathway is a network of receptors, adaptor proteins, and downstream effectors that rapidly detect conserved microbial or danger signals and trigger immediate, non-specific inflammatory and antiviral responses.
-
E.
immune checkpoint receptor
An immune checkpoint receptor is a cell-surface protein, typically on immune cells like T cells, that modulates immune responses by delivering inhibitory or stimulatory signals upon binding to its ligand, thereby maintaining self-tolerance and preventing overactivation.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.