Triple
T11074836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APHINITY trial |
E261835
|
entity |
| Predicate | therapyLine |
P97066
|
FINISHED |
| Object | curative-intent 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: curative-intent adjuvant therapy | Statement: [APHINITY trial, therapyLine, curative-intent adjuvant therapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapyLine Context triple: [APHINITY trial, therapyLine, curative-intent adjuvant therapy]
-
A.
treats
Indicates that one entity provides medical care or therapeutic intervention to another entity.
-
B.
treatment
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
-
C.
treatmentLevel
Indicates the degree or intensity of a treatment applied or received in a given context.
-
D.
therapeuticOrientation
Indicates the specific therapeutic approach or framework a practitioner uses when providing psychological or counseling treatment.
-
E.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
- F. None of above. chosen
Provenance (4 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994efb608190a81bc8c4d16ddbd0 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.