Triple
T1266343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham City Jail |
E15608
|
entity |
| Predicate | hasTypeOfInmates |
P18550
|
FINISHED |
| Object | adult detainees |
—
|
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 detainees | Statement: [Birmingham City Jail, hasTypeOfInmates, adult detainees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfInmates Context triple: [Birmingham City Jail, hasTypeOfInmates, adult detainees]
-
A.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
B.
hasNotableCategoryOfPrisoners
chosen
Indicates that a prison is known for housing a specific, notable category or type of prisoners.
-
C.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
D.
hasPrisonerPopulation
Indicates that an entity maintains or contains a population of prisoners, specifying the number or presence of incarcerated individuals associated with it.
-
E.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c037f14c8190baa42f70f8846583 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.