Triple
T15792596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year Zero |
E382895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Khmer Rouge policy |
C24763
|
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: Khmer Rouge policy Context triple: [Year Zero, instanceOf, Khmer Rouge policy]
-
A.
Maoist policy initiative
chosen
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.
-
B.
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.
-
C.
Khmer Rouge leader
A Khmer Rouge leader is a high-ranking figure within the radical communist movement that ruled Cambodia from 1975 to 1979, responsible for directing policies and actions that led to widespread atrocities and genocide.
-
D.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
E.
Siamese state
A Siamese state is a quantum state composed of two or more subsystems that are structurally identical and correlated in a way that enables comparative or joint processing, often used in tasks like state discrimination or metric learning.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.