Triple

T36599973
Position Surface form Disambiguated ID Type / Status
Subject CD22 E902890 entity
Predicate instanceOf P0 FINISHED
Object inhibitory co-receptor C59321 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: inhibitory co-receptor
Context triple: [CD22, instanceOf, inhibitory co-receptor]
  • A. immune checkpoint receptor chosen
    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.
  • B. 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.
  • C. Bruton’s tyrosine kinase
    Bruton’s tyrosine kinase is a non-receptor tyrosine kinase crucial for B-cell receptor signaling, development, and function, and is a key therapeutic target in certain autoimmune diseases and B-cell malignancies.
  • D. transmembrane receptor
    A transmembrane receptor is a membrane-spanning protein that detects extracellular signals and transduces them into specific intracellular responses.
  • E. Bruton tyrosine kinase inhibitor
    A Bruton tyrosine kinase inhibitor is a targeted small-molecule drug that blocks BTK signaling in B cells to disrupt pathways critical for their activation, proliferation, and survival, primarily used in the treatment of certain B-cell malignancies and autoimmune diseases.
  • 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.