Triple
T25406994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guy Simonds |
E636585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian military commander |
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: Canadian military commander Context triple: [Guy Simonds, instanceOf, Canadian military commander]
-
A.
military commander in New France
A military commander in New France was a royal appointee responsible for organizing, leading, and coordinating French colonial troops and allied Indigenous forces to defend and expand the colony’s territories in North America.
-
B.
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.
-
C.
French military leader
A French military leader is a high-ranking officer from France responsible for planning, directing, and commanding military operations and forces in defense of national interests.
-
D.
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.
-
E.
Canadian military institution
A Canadian military institution is an organization established by the Government of Canada to develop, manage, and support the nation’s armed forces through training, policy, operations, and defense-related services.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:52 p.m.