Triple
T37345464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksandr Petrovich Goryanchikov |
E927159
|
entity |
| Predicate | convictionContext |
P187754
|
FINISHED |
| Object | Siberian prison camp |
—
|
NE NERFINISHED |
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: Siberian prison camp | Statement: [Aleksandr Petrovich Goryanchikov, convictionContext, Siberian prison camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convictionContext Context triple: [Aleksandr Petrovich Goryanchikov, convictionContext, Siberian prison camp]
-
A.
convictionJurisdiction
Indicates the legal authority or geographic area under whose jurisdiction a conviction was issued.
-
B.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
C.
initialConviction
Indicates the original judgment or decision of guilt assigned to an entity before any appeals, modifications, or subsequent legal actions.
-
D.
reasonForConviction
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
E.
judgmentContext
Indicates the situational, legal, or evaluative framework within which a judgment or decision is made.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.