Triple
T6694274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Pakenham |
E152708
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military commander in the Napoleonic Wars |
C16128
|
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: military commander in the Napoleonic Wars Context triple: [Edward Pakenham, instanceOf, military commander in the Napoleonic Wars]
-
A.
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.
-
B.
19th-century military leader
chosen
A 19th-century military leader is a high-ranking commander who directed armed forces during the 1800s, shaping national and imperial conflicts through strategic planning, battlefield leadership, and political influence.
-
C.
military commander in the Great Northern War
A military commander in the Great Northern War is a high-ranking officer responsible for planning and directing land or naval operations among the warring Northern and Eastern European powers between 1700 and 1721.
-
D.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:05 p.m.