Triple
T33388595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genmab A/S |
E854985
|
entity |
| Predicate | treatsDiseaseArea |
P20980
|
FINISHED |
| Object | hematologic malignancies |
—
|
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: hematologic malignancies | Statement: [Genmab A/S, treatsDiseaseArea, hematologic malignancies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsDiseaseArea Context triple: [Genmab A/S, treatsDiseaseArea, hematologic malignancies]
-
A.
coreTherapeuticArea
Indicates the primary medical or clinical domain in which a therapy, treatment, or product is principally intended to be used.
-
B.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
-
C.
diseaseUsed
Indicates that a particular disease is employed or utilized as a tool, model, or condition within a given context or process.
-
D.
hasTargetDisease
chosen
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
E.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:35 a.m.