Triple
T12393326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tizard Mission |
E296051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II diplomatic mission |
C31398
|
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 diplomatic mission Context triple: [Tizard Mission, instanceOf, World War II diplomatic mission]
-
A.
World War II conference
A World War II conference is a high-level diplomatic meeting held among Allied or Axis leaders during the war to coordinate military strategy, negotiate political arrangements, and shape postwar plans.
-
B.
World War II resistance operation
A World War II resistance operation is a covert, organized action conducted by underground groups in occupied territories to sabotage enemy forces, gather intelligence, and support Allied war efforts.
-
C.
World War II military plan
A World War II military plan is a strategically designed, time-bound set of coordinated operations and resource allocations intended to achieve specific political and military objectives within the context of the global conflict.
-
D.
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.
-
E.
World War II military role
A World War II military role represents a specific set of duties, responsibilities, and functions performed by individuals or units within the armed forces of nations involved in the conflict between 1939 and 1945.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:54 p.m.