Triple
T33660002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pickering Plan for reorganizing the Continental Army |
E862324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military reorganization plan |
C4456
|
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 reorganization plan Context triple: [Pickering Plan for reorganizing the Continental Army, instanceOf, military reorganization plan]
-
A.
military reorganization
chosen
Military reorganization is the systematic restructuring of a nation's armed forces—its units, command structures, resources, and doctrines—to improve effectiveness, adapt to new threats, or align with political and strategic objectives.
-
B.
military rearmament program
A military rearmament program is a coordinated, government-directed initiative to expand, modernize, or restore a nation’s armed forces and weaponry in response to strategic, political, or security objectives.
-
C.
planned military formation
A planned military formation is a deliberately organized arrangement of troops, vehicles, or units in space and time designed to achieve specific tactical or strategic objectives under anticipated conditions.
-
D.
military reformer
A military reformer is an individual who critically evaluates existing armed forces structures, doctrines, and practices and implements innovative changes to improve their effectiveness, efficiency, and adaptability.
-
E.
military mobilization
Military mobilization is the organized process by which a state prepares and deploys its armed forces and resources for war or national defense.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.