Triple
T2371030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rituxan |
E46089
|
entity |
| Predicate | hasMoleculeType |
P16808
|
FINISHED |
| Object | IgG1 kappa monoclonal antibody |
—
|
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: IgG1 kappa monoclonal antibody | Statement: [Rituxan, hasMoleculeType, IgG1 kappa monoclonal antibody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoleculeType Context triple: [Rituxan, hasMoleculeType, IgG1 kappa monoclonal antibody]
-
A.
hasMolecularWeight
Indicates that an entity possesses a specific molecular weight value, typically expressed in standardized units such as daltons or g/mol.
-
B.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
C.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
D.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76f5aec8190867d621e6849258c |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.