Triple
T17168048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orde Charles Wingate |
E416656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commander in World War II |
C22817
|
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: commander in World War II Context triple: [Orde Charles Wingate, instanceOf, commander in World War II]
-
A.
World War II military command
A World War II military command is an organized, hierarchical structure of armed forces responsible for planning, directing, and coordinating operations within a defined theater, branch, or mission during the Second World War.
-
B.
Military leader
chosen
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.
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.
-
D.
war leader
A war leader is an individual who plans, directs, and inspires military forces in armed conflict, making strategic and tactical decisions to achieve political or territorial objectives.
-
E.
Polish military leader
A Polish military leader is a high-ranking commander from Poland responsible for planning, directing, and overseeing military operations and the strategic use of armed forces in defense of the nation.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:37 a.m.