Triple
T5695251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergei Sedov |
E125523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | victim of political repression |
C2328
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: victim of political repression Context triple: [Sergei Sedov, instanceOf, victim of political repression]
-
A.
victims of political repression
chosen
Individuals who have been unjustly targeted, persecuted, or punished by state or political authorities due to their beliefs, affiliations, or activities that are perceived as oppositional or threatening to the existing power structure.
-
B.
perpetrator of political repression
A perpetrator of political repression is an individual, group, or institution that intentionally uses coercive, violent, or manipulative means to silence, control, or punish people for their political beliefs, activities, or affiliations.
-
C.
mass political repression
Mass political repression is the systematic, large-scale use of coercion, surveillance, and violence by authorities to silence, control, or eliminate political opposition and dissent within a population.
-
D.
political prisoner
A political prisoner is an individual detained or imprisoned primarily because of their political beliefs, activities, or opposition to the governing authority, rather than for a recognized criminal offense.
-
E.
victim of police violence
A victim of police violence is an individual who has suffered physical, psychological, or civil rights harm as a result of excessive, unlawful, or discriminatory actions by law enforcement officers.
- F. None of above.
Provenance (1 batch)
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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:45 p.m.