Triple
T4385787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wawer massacre |
E99238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II atrocity |
C873
|
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 atrocity Context triple: [Wawer massacre, instanceOf, World War II atrocity]
-
A.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
B.
World War II event
chosen
A World War II event is a historically significant occurrence between 1939 and 1945 that directly influenced the political, military, social, or economic course of the global conflict.
-
C.
World War II weapon
A World War II weapon is any tool, device, or system—ranging from small arms and artillery to aircraft, naval vessels, and emerging technologies like rockets and atomic bombs—designed and employed by nations between 1939 and 1945 to inflict damage, gain strategic advantage, or defend against enemy forces.
-
D.
aspect of World War II
An aspect of World War II is a distinct thematic component—such as military strategy, political leadership, home-front life, technology, or ideology—that helps explain how the conflict was conducted, experienced, and remembered.
-
E.
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.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:19 p.m.