Triple
T12767119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma State Penitentiary |
E305152
|
entity |
| Predicate | hasInmateClassification |
P105493
|
FINISHED |
| Object | maximum 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: maximum security | Statement: [Oklahoma State Penitentiary, hasInmateClassification, maximum security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInmateClassification Context triple: [Oklahoma State Penitentiary, hasInmateClassification, maximum security]
-
A.
hasPrisonerCategory
Indicates the classification or category assigned to a prisoner within a correctional or detention system.
-
B.
hasInmateCustodyLevel
chosen
Indicates the security or supervision level at which an inmate is held in custody.
-
C.
hasInmateGender
Indicates that an inmate possesses a specified gender.
-
D.
hasInmateManagementPolicy
Indicates that an entity has established rules or procedures governing the management and treatment of inmates.
-
E.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df3b2f88190b37b696400178795 |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.