Triple
T22674036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | regional correction headquarters |
E560298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of correctional system |
C46657
|
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: component of correctional system Context triple: [regional correction headquarters, instanceOf, component of correctional system]
-
A.
component of the criminal justice system
A component of the criminal justice system is any institutional entity, process, or role—such as law enforcement, courts, or corrections—that collectively functions to define, enforce, adjudicate, and sanction violations of criminal law.
-
B.
penal system
The penal system is the organized set of laws, institutions, and practices a society uses to punish, manage, and attempt to rehabilitate individuals who violate criminal laws.
-
C.
correctional facility
A correctional facility is a secure institution where individuals convicted of crimes are confined, supervised, and provided with programs aimed at punishment, rehabilitation, and public safety.
-
D.
justice and corrections support mechanism
A justice and corrections support mechanism is a structured system of tools, services, and processes designed to assist legal and correctional institutions in ensuring fair adjudication, effective rehabilitation, and secure, humane management of offenders.
-
E.
penal institution
A penal institution is a secure facility where individuals convicted of crimes are confined and managed as part of a society’s system of punishment, deterrence, and rehabilitation.
- F. None of above. chosen
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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:10 p.m.