Triple
T11138612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Right Socialist Revolutionaries |
E263480
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian political organization |
C27416
|
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 political organization Context triple: [Right Socialist Revolutionaries, instanceOf, Russian political organization]
-
A.
Soviet organization
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
-
B.
Ukrainian nationalist organization
A Ukrainian nationalist organization is a group dedicated to promoting and defending the political, cultural, and historical interests, identity, and sovereignty of the Ukrainian nation.
-
C.
organization based in Russia
An organization based in Russia is any structured group or entity—such as a company, nonprofit, institution, or association—whose primary operations, legal registration, or headquarters are located within the Russian Federation.
-
D.
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.
-
E.
anti-Bolshevik political organization
chosen
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.
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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:28 p.m.