Triple
T25609951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IK-2 Pokrov |
E642019
|
entity |
| Predicate | prisonSystem |
P127588
|
FINISHED |
| Object | Russian penal colony system |
—
|
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: Russian penal colony system | Statement: [IK-2 Pokrov, prisonSystem, Russian penal colony system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prisonSystem Context triple: [IK-2 Pokrov, prisonSystem, Russian penal colony system]
-
A.
partOfPenalSystem
chosen
Indicates that something belongs to, is included within, or functions as a component of a jurisdiction’s penal or criminal justice system.
-
B.
countryPrisonSystem
Indicates a relationship where a country has, administers, or is associated with a particular prison system.
-
C.
prisonType
Indicates the specific category or classification of a prison associated with an entity.
-
D.
hasPrisonManagementSystem
Indicates that an entity operates, utilizes, or is associated with a prison management system for administering correctional facilities or inmate-related processes.
-
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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9e1f1408190bab690f67f7d3a31 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:40 p.m.