Triple
T31440207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CD3 complex |
E802043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | T-cell surface receptor component |
C27666
|
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: T-cell surface receptor component Context triple: [CD3 complex, instanceOf, T-cell surface receptor component]
-
A.
cluster of differentiation antigen
chosen
A cluster of differentiation antigen is a cell surface molecule used as a marker to identify and classify leukocyte subsets and other cell types, often serving functional roles in cell signaling and immune responses.
-
B.
Fc gamma receptor
Fc gamma receptor is a cell-surface receptor that specifically binds the Fc region of IgG antibodies, mediating immune functions such as phagocytosis, antibody-dependent cellular cytotoxicity, and modulation of inflammatory responses.
-
C.
T lymphocyte subset
A T lymphocyte subset is a functionally distinct group of T cells characterized by specific surface markers, cytokine profiles, and immune roles, such as helper, cytotoxic, or regulatory functions.
-
D.
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.
-
E.
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.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:05 p.m.