Triple
T11074575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-CHOP |
E261830
|
entity |
| Predicate | targetsMolecule |
P37016
|
FINISHED |
| Object | CD20 antigen on B cells |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: CD20 antigen on B cells | Statement: [R-CHOP, targetsMolecule, CD20 antigen on B cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsMolecule Context triple: [R-CHOP, targetsMolecule, CD20 antigen on B cells]
-
A.
hasMolecularTarget
chosen
Indicates that one entity (such as a drug or compound) is directed toward, binds to, or specifically interacts with a particular molecular target (such as a protein, receptor, or gene).
-
B.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
-
C.
targetOrganism
Indicates that an action, process, or effect is directed toward or intended to impact a particular organism.
-
D.
targetsDiseaseVector
Indicates that an entity is directed at, designed to affect, or intended to control a particular disease-carrying vector organism.
-
E.
regulatoryTarget
Indicates that one entity is subject to control, influence, or governance by another entity under a regulatory or rule-based framework.
- F. None of above.
Provenance (3 batches)
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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994efb608190a81bc8c4d16ddbd0 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.