Triple
T5028467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HM Prison Usk |
E113234
|
entity |
| Predicate | inmateClassification |
P32689
|
FINISHED |
| Object | adult male prisoners |
—
|
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: adult male prisoners | Statement: [HM Prison Usk, inmateClassification, adult male prisoners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inmateClassification Context triple: [HM Prison Usk, inmateClassification, adult male prisoners]
-
A.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
B.
hasPrisonerCategory
chosen
Indicates the classification or category assigned to a prisoner within a correctional or detention system.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
hasNotableCategoryOfPrisoners
Indicates that a prison is known for housing a specific, notable category or type of prisoners.
-
E.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738f2cc88190a03eebf19e407411 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.