Triple
T36600535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APHINITY |
E902901
|
entity |
| Predicate | therapySetting |
P97059
|
FINISHED |
| Object | adjuvant therapy |
—
|
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: adjuvant therapy | Statement: [APHINITY, therapySetting, adjuvant therapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapySetting Context triple: [APHINITY, therapySetting, adjuvant therapy]
-
A.
therapyWith
Indicates that one entity receives or engages in therapeutic treatment or counseling with another entity (such as a therapist, therapy method, or therapeutic resource).
-
B.
treatmentSetting
chosen
Indicates the type of environment or context in which a treatment or intervention is delivered.
-
C.
clinicalSetting
Indicates that an action, observation, or interaction occurs within a healthcare or medical care environment.
-
D.
therapyLine
Indicates that one entity is a specific therapeutic product, regimen, or line of treatment used in the medical management of another entity.
-
E.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.