Triple
T16116566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Expeditionary Force |
E391015
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military command |
C37002
|
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 military command Context triple: [Allied Expeditionary Force, instanceOf, World War II military command]
-
A.
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.
-
B.
Military leader
A military leader is an individual who plans, directs, and coordinates armed forces operations, making strategic and tactical decisions to achieve military objectives while managing and motivating personnel under their command.
-
C.
Chief of the German General Staff
The Chief of the German General Staff was the highest-ranking professional officer responsible for planning, directing, and coordinating the operations and strategy of the German Army’s General Staff.
-
D.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
-
E.
military leader of World War I
A military leader of World War I is a high-ranking officer or commander responsible for planning, directing, and overseeing large-scale military operations and strategies for a nation or alliance during the 1914–1918 global conflict.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5 a.m.