Triple
T20061779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEACOPP regimen |
E499491
|
entity |
| Predicate | treatmentGoal |
P24604
|
FINISHED |
| Object | increase cure rate |
—
|
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: increase cure rate | Statement: [BEACOPP regimen, treatmentGoal, increase cure rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentGoal Context triple: [BEACOPP regimen, treatmentGoal, increase cure rate]
-
A.
hasTherapeuticGoal
chosen
Indicates that an action, treatment, or intervention is undertaken with the intention of achieving a specific therapeutic or health-related outcome.
-
B.
aimsToTreat
Indicates that one entity (typically an intervention, treatment, or action) is intended or designed to alleviate, cure, or manage a condition, problem, or target entity.
-
C.
goalOfTrials
Indicates that the specified goal is the intended objective or outcome that the trials are designed to achieve or evaluate.
-
D.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
E.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6637601dc8190a07fc20844093cb7 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.