Triple
T29841530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Correctional Institution, Pensacola |
E757810
|
entity |
| Predicate | inmatePopulationSecurityLevel |
P105493
|
FINISHED |
| Object | minimum security |
—
|
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: minimum security | Statement: [Federal Correctional Institution, Pensacola, inmatePopulationSecurityLevel, minimum security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inmatePopulationSecurityLevel Context triple: [Federal Correctional Institution, Pensacola, inmatePopulationSecurityLevel, minimum security]
-
A.
hasInmateCustodyLevel
chosen
Indicates the security or supervision level at which an inmate is held in custody.
-
B.
securityForInmates
Indicates the provision or management of protective measures and safeguards specifically intended for inmates.
-
C.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
D.
inmateAgeGroup
Indicates the age-range category to which an inmate belongs.
-
E.
detainedPopulation
Indicates that a population of individuals is being held in custody or confinement, typically by legal or governmental authority.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760a7ee88190992cdec8aaaf49fa |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:39 p.m.