Triple
T27479963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Front of World War II |
E693573
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | front of World War II |
C4875
|
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: front of World War II Context triple: [Eastern Front of World War II, instanceOf, front of World War II]
-
A.
World War II front
chosen
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
B.
World War II-era state
A World War II-era state is a sovereign political entity operating between roughly 1933 and 1945 whose institutions, economy, military, and society were shaped by the global conflict, wartime alliances, and total war mobilization.
-
C.
phase of World War II
A phase of World War II is a distinct, time-bounded period of the conflict characterized by specific strategic objectives, major campaigns, and shifts in military, political, or economic conditions.
-
D.
World War II-era policy
A World War II-era policy is a governmental or institutional rule, strategy, or directive formulated and implemented between roughly 1933 and 1945 in response to the political, military, economic, and social conditions of the Second World War.
-
E.
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.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 12:59 p.m.