Triple
T10108598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Tax in Kind |
E218184
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bolshevik policy document |
C13140
|
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: Bolshevik policy document Context triple: [On the Tax in Kind, instanceOf, Bolshevik policy document]
-
A.
Soviet document
chosen
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
B.
Soviet government position
A Soviet government position is an official role within the political and administrative hierarchy of the USSR, responsible for implementing Communist Party policies and managing state functions at various levels.
-
C.
policy of the Soviet Union
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
-
D.
Soviet revolutionary
A Soviet revolutionary is an individual who actively participated in or supported the political, social, and often armed struggle to overthrow the existing order and establish or advance the socialist state in the former Soviet Union.
-
E.
Maoist policy initiative
A Maoist policy initiative is a government or party-driven program designed to implement Mao Zedong’s principles of class struggle, mass mobilization, and collectivist economic and social transformation.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.