Triple
T26391574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shout mental health text service |
E663425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mental health support service |
C43147
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: mental health support service Context triple: [Shout mental health text service, instanceOf, mental health support service]
-
A.
mental health trust
A mental health trust is a specialized healthcare organization within the UK’s National Health Service that provides assessment, treatment, and support services for people with mental health conditions in a defined geographic area.
-
B.
public mental health authority
A public mental health authority is a government-designated organization responsible for planning, funding, coordinating, and overseeing mental health services for a defined population or region.
-
C.
health and social support agency
chosen
A health and social support agency is an organization that provides medical, psychological, and social services to individuals and communities to promote well-being and address health-related and social needs.
-
D.
hospital-based mental health program
A hospital-based mental health program is a coordinated set of clinical and support services delivered within a hospital setting to assess, treat, and stabilize individuals experiencing mental health conditions or crises.
-
E.
student support service
A student support service is an institutional resource that provides academic, emotional, financial, and practical assistance to help students succeed and well-being throughout their educational journey.
- F. None of above.
Provenance (1 batch)
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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:26 p.m.