Triple
T38165313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | For Fair Elections movement |
E953126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian opposition campaign |
C52145
|
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: Russian opposition campaign Context triple: [For Fair Elections movement, instanceOf, Russian opposition campaign]
-
A.
Russian opposition organization
chosen
A Russian opposition organization is a group that operates within or in relation to Russia to challenge, criticize, or seek to change the existing political regime, policies, or power structures, typically advocating for democratic reforms, human rights, and rule of law.
-
B.
Soviet election
A Soviet election was a state-controlled, non-competitive electoral process in the USSR, typically featuring a single approved candidate per seat and serving primarily to legitimize Communist Party rule rather than to offer genuine voter choice.
-
C.
Russian military campaign
A Russian military campaign is a coordinated series of strategic and tactical operations conducted by Russia’s armed forces to achieve specific political, territorial, or security objectives.
-
D.
election in the Soviet Union
An election in the Soviet Union was a state-controlled political process in which candidates, typically preselected by the Communist Party, were formally approved by voters in largely non-competitive, single-party ballots.
-
E.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.