Triple
T25306866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atascadero State Hospital |
E634502
|
entity |
| Predicate | treatmentProgram |
P149376
|
FINISHED |
| Object | sex offender treatment programs |
—
|
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: sex offender treatment programs | Statement: [Atascadero State Hospital, treatmentProgram, sex offender treatment programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentProgram Context triple: [Atascadero State Hospital, treatmentProgram, sex offender treatment programs]
-
A.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
-
B.
supportingProgram
Indicates that one program provides assistance, resources, or backing to another program or initiative.
-
C.
hasResidentialProgram
Indicates that an entity offers or is associated with a residential program where participants live on-site.
-
D.
stateProgram
Indicates that a program is organized, funded, or administered by a governmental state authority.
-
E.
applicablePrograms
chosen
Indicates that certain programs are relevant to, valid for, or can be applied in the context of a given entity or situation.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:25 p.m.