Triple
T1266336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham City Jail |
E15608
|
entity |
| Predicate | dateOfNotableIncarceration |
P24912
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Birmingham City Jail, dateOfNotableIncarceration, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfNotableIncarceration Context triple: [Birmingham City Jail, dateOfNotableIncarceration, 1963]
-
A.
dateOfImprisonmentStart
Indicates the date on which an entity’s period of imprisonment begins.
-
B.
dateOfConviction
Indicates the specific calendar date on which a person or entity was formally found guilty of an offense.
-
C.
dateOfArrest
Indicates the specific date on which an entity was formally arrested by an authority.
-
D.
peakIncarcerationPeriod
Indicates the time period during which incarceration levels for the referenced entity were at their highest.
-
E.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4bc218cb8819090bff71ac7107a03 |
completed | March 1, 2026, 10:22 p.m. |
Created at: March 1, 2026, 7:50 p.m.