Triple
T6273548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief on the Western Front |
E140597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I military command |
C5649
|
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 I military command Context triple: [Commander-in-Chief on the Western Front, instanceOf, World War I military command]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
participant in World War I
A participant in World War I is any nation, military force, or individual actively involved in the political, military, or logistical operations of the global conflict between 1914 and 1918.
-
E.
World War I theater
chosen
A World War I theater is a large-scale geographic region where military operations, campaigns, and battles of the First World War were conducted under a unified strategic command.
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:25 p.m.