Triple
T2785103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Order No. 1 |
E61791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II surrender directive |
C853
|
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 surrender directive Context triple: [General Order No. 1, instanceOf, World War II surrender directive]
-
A.
military surrender
Military surrender is the formal act by which an armed force or nation yields control and ceases resistance to an opposing force, typically under agreed conditions.
-
B.
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.
-
C.
World War II document
chosen
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.
-
D.
World War II offensive
A World War II offensive is a coordinated, large-scale military campaign conducted by one or more nations to seize strategic objectives, weaken enemy forces, or shift the balance of the war in a specific theater or front.
-
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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:57 p.m.