Triple
T15920561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melody Gardot |
E386080
|
entity |
| Predicate | therapyUsed |
P4714
|
FINISHED |
| Object | music 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: music therapy | Statement: [Melody Gardot, therapyUsed, music therapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapyUsed Context triple: [Melody Gardot, therapyUsed, music therapy]
-
A.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
-
B.
treatment
chosen
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
-
C.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
-
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.
treats
Indicates that one entity provides medical care or therapeutic intervention 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.