Triple
T8000817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Jellicoe, 1st Earl Jellicoe |
E186243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I military leader |
C13907
|
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 leader Context triple: [John Jellicoe, 1st Earl Jellicoe, instanceOf, World War I military leader]
-
A.
military leader of World War I
chosen
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.
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.
British military leader
A British military leader is a high-ranking officer from the United Kingdom responsible for planning, directing, and overseeing military operations and strategy, often commanding troops in national defense or international conflicts.
-
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.
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.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:17 p.m.