Triple
T4374621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Why We Fight (film series) |
E98974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II propaganda |
C15829
|
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 propaganda Context triple: [Why We Fight (film series), instanceOf, World War II propaganda]
-
A.
World War II document
A World War II document is an original or reproduced written, printed, or recorded artifact created during or directly concerning the events, policies, operations, or experiences of the Second World War.
-
B.
World War II propaganda figure
A World War II propaganda figure is a personified or symbolic character—real or fictional—used in wartime media to influence public opinion, boost morale, demonize the enemy, or promote specific political and military objectives.
-
C.
theater of World War II
The theater of World War II is a conceptual class representing a distinct geographic region and operational context in which military campaigns, battles, and strategic activities of the war were planned, conducted, and coordinated.
-
D.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
E.
World War I poster
A World War I poster is a visually striking, often propagandistic print designed to influence public opinion or behavior during the war, typically through patriotic imagery, bold text, and emotional appeals.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:18 p.m.