Triple
T31157332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Bureau of Prisons South Central Region |
E794245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional office of the Federal Bureau of Prisons |
C38196
|
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: regional office of the Federal Bureau of Prisons Context triple: [Federal Bureau of Prisons South Central Region, instanceOf, regional office of the Federal Bureau of Prisons]
-
A.
administrative region of the Federal Bureau of Prisons
chosen
An administrative region of the Federal Bureau of Prisons is a geographically defined division responsible for overseeing, coordinating, and managing federal correctional institutions and related operations within its designated area.
-
B.
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.
-
C.
department of corrections
A department of corrections is a government agency responsible for overseeing the incarceration, rehabilitation, and supervision of individuals convicted of crimes.
-
D.
detention facility
A detention facility is a secure institution designed to confine individuals who are awaiting trial, sentencing, or serving a criminal sentence under legal authority.
-
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.
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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:07 p.m.