Triple
T10047370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Schofield |
E207649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Commanding General of the United States Army |
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: Commanding General of the United States Army Context triple: [John Schofield, instanceOf, Commanding General of the United States Army]
-
A.
general of the army
A general of the army is the highest-ranking military officer responsible for overseeing large-scale strategic planning, command, and coordination of an entire nation's land forces.
-
B.
Commander-in-chief
The Commander-in-chief is the highest-ranking authority responsible for the overall command, strategic direction, and ultimate decision-making of a nation's armed forces.
-
C.
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.
-
D.
major command of the United States Army
A major command of the United States Army is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale operational, administrative, or functional missions across multiple subordinate units and installations.
-
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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:56 p.m.