Triple
T5398026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disciplinary Training Center, Pisa |
E120704
|
entity |
| Predicate | yearOfNotableDetention |
P31117
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Disciplinary Training Center, Pisa, yearOfNotableDetention, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfNotableDetention Context triple: [Disciplinary Training Center, Pisa, yearOfNotableDetention, 1945]
-
A.
dateOfNotableIncarceration
Indicates the specific date on which an entity began a notable or historically significant period of incarceration.
-
B.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
C.
peakIncarcerationPeriod
Indicates the time period during which incarceration levels for the referenced entity were at their highest.
-
D.
imprisonmentYear
chosen
Indicates the specific year in which an entity was imprisoned or placed into custody.
-
E.
notablePrisoner
Indicates that a person is recognized as a significant or noteworthy inmate of a particular prison or detention facility.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.