Triple
T2370971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herceptin |
E46088
|
entity |
| Predicate | hasCASNumber |
P19728
|
FINISHED |
| Object | 180288-69-1 |
—
|
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: 180288-69-1 | Statement: [Herceptin, hasCASNumber, 180288-69-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCASNumber Context triple: [Herceptin, hasCASNumber, 180288-69-1]
-
A.
CASNumber
chosen
Indicates that a chemical substance is identified by a specific unique CAS (Chemical Abstracts Service) registry number.
-
B.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
C.
hasATCCode
Indicates that a pharmaceutical product or substance is assigned a specific Anatomical Therapeutic Chemical (ATC) classification code.
-
D.
hasChemicalFormula
Indicates that one entity (typically a chemical substance) is characterized by or associated with a specific chemical formula representing its elemental composition.
-
E.
hasAtomicNumber
Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other entity.
- 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.