Triple
T20854022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rankian psychotherapy |
E513431
|
entity |
| Predicate | therapeuticSetting |
P97059
|
FINISHED |
| Object | individual 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: individual psychotherapy | Statement: [Rankian psychotherapy, therapeuticSetting, individual psychotherapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: therapeuticSetting Context triple: [Rankian psychotherapy, therapeuticSetting, individual psychotherapy]
-
A.
treatmentSetting
chosen
Indicates the type of environment or context in which a treatment or intervention is delivered.
-
B.
clinicalSetting
Indicates that an action, observation, or interaction occurs within a healthcare or medical care environment.
-
C.
providesCareSetting
Indicates that one entity serves as the care environment or setting in which another entity receives or delivers care.
-
D.
therapeuticOrientation
Indicates the specific therapeutic approach or framework a practitioner uses when providing psychological or counseling treatment.
-
E.
includesTherapy
Indicates that one entity contains, offers, or encompasses a specific therapeutic treatment or intervention as part of its scope or composition.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a6015081909f604a88d04b36ea |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.