Triple
T127169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBI Theater |
E2575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II theater of operations |
C635
|
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 theater of operations Context triple: [CBI Theater, instanceOf, World War II theater of operations]
-
A.
World War II campaign
chosen
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.
-
B.
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.
-
C.
World War II faction
A World War II faction is a distinct political, military, or ideological group—such as a nation, alliance, or resistance movement—that organized and acted collectively to pursue its strategic objectives during the global conflict of 1939–1945.
-
D.
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.
-
E.
World War II event
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.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.