Triple
T31465250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Group Conference |
E802705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | youth justice practice |
C47185
|
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: youth justice practice Context triple: [Family Group Conference, instanceOf, youth justice practice]
-
A.
youth justice intervention
A youth justice intervention is a structured program or action designed to address and reduce offending or at-risk behavior among young people by promoting accountability, rehabilitation, and positive social outcomes.
-
B.
youth jury
A youth jury is a group of young people formally convened to deliberate on issues, cases, or policies and provide recommendations or decisions from a youth-centered perspective.
-
C.
juvenile justice agency
A juvenile justice agency is a government or community-based organization responsible for preventing, processing, supervising, and rehabilitating youth involved in or at risk of involvement in the legal system.
-
D.
juvenile justice legislation
Juvenile justice legislation comprises the laws and policies that govern how young people who commit offenses are treated, emphasizing rehabilitation, age-appropriate accountability, and protection of their legal rights.
-
E.
restorative justice practice
chosen
Restorative justice practice is a collaborative process that brings together those harmed, those responsible, and the community to acknowledge harm, address needs and obligations, and work toward healing and reintegration rather than punishment.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:22 p.m.