Triple
T27028290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Victory |
E680848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II home front campaign |
C15795
|
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: World War II home front campaign Context triple: [Double Victory, instanceOf, World War II home front campaign]
-
A.
World War II home front initiative
A World War II home front initiative is a coordinated civilian effort, organized by governments or communities, to support the war through activities such as resource conservation, industrial production, volunteer work, and morale-building campaigns.
-
B.
World War II propaganda campaign
chosen
A World War II propaganda campaign is a coordinated effort by governments or organizations to shape public opinion, morale, and behavior during the war through controlled messages, imagery, and media.
-
C.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
D.
World War II rear area
A World War II rear area is the zone behind the front lines where military forces organized logistics, supply, administration, medical care, training, and security operations to support combat units at the front.
-
E.
World War II home front workforce
The World War II home front workforce comprises the civilian men and women who filled industrial, agricultural, and support roles to sustain military production and national economies while many traditional workers served in the armed forces.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:12 a.m.