Triple
T7169824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IK-6 penal colony, Melekhovo |
E167163
|
entity |
| Predicate | typeOfImprisonment |
P19110
|
FINISHED |
| Object | corrective colony |
—
|
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: corrective colony | Statement: [IK-6 penal colony, Melekhovo, typeOfImprisonment, corrective colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfImprisonment Context triple: [IK-6 penal colony, Melekhovo, typeOfImprisonment, corrective colony]
-
A.
durationOfImprisonment
Indicates the length of time that an entity is or was held in imprisonment.
-
B.
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.
-
C.
prisonType
chosen
Indicates the specific category or classification of a prison associated with an entity.
-
D.
imprisonmentYear
Indicates the specific year in which an entity was imprisoned or placed into custody.
-
E.
detentionType
Indicates the specific category or form of detention applied to an entity within a custodial or restrictive context.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85d8f208190915f6f4c05988b63 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1ce5f048190808c378a980f7bb6 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.