Triple
T38596739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward A |
E934099
|
entity |
| Predicate | hasTreatmentModalities |
P122242
|
FINISHED |
| Object | psychotherapy |
—
|
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: psychotherapy | Statement: [Ward A, hasTreatmentModalities, psychotherapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreatmentModalities Context triple: [Ward A, hasTreatmentModalities, psychotherapy]
-
A.
hasCommonTreatment
Indicates that two or more entities share at least one treatment method or therapeutic approach in common.
-
B.
hasReceivedTreatmentFor
Indicates that an entity has undergone or been given a treatment in relation to a specified condition, issue, or problem.
-
C.
treatmentType
chosen
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
D.
usesTreatment
Indicates that one entity applies or employs a particular treatment or therapeutic method on or for another entity.
-
E.
hasMainTherapeuticApproach
Indicates that an entity is associated with its primary or principal therapeutic method or treatment strategy.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:32 p.m.