Triple
T26870404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Russia network |
E676595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian opposition organization |
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 organization Context triple: [Open Russia network, instanceOf, Russian opposition organization]
-
A.
Russian political party
A Russian political party is an organized group within the Russian Federation that seeks to influence or control government policy and leadership through participation in elections and the political process, typically based on a specific ideology or set of interests.
-
B.
Rusyn organization
A Rusyn organization is a formal group or institution dedicated to representing, preserving, and promoting the cultural, social, political, or educational interests of the Rusyn people.
-
C.
anti-Bolshevik organization
An anti-Bolshevik organization is a group formed to oppose Bolshevik ideology, policies, or rule, typically through political, military, or propaganda activities.
-
D.
Crimean Tatar organization
A Crimean Tatar organization is a formal group or institution established by or for Crimean Tatars to represent their interests, preserve their culture and language, and address social, political, or community issues.
-
E.
anti-Bolshevik political organization
An anti-Bolshevik political organization is a group formed to oppose Bolshevik ideology and governance, typically advocating alternative political, economic, or social systems and often engaging in propaganda, activism, or coordinated resistance.
- F. None of above. chosen
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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:32 a.m.