Triple
T2908262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II Corps (United States) |
E63618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corps of the United States Army |
C2497
|
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: corps of the United States Army Context triple: [II Corps (United States), instanceOf, corps of the United States Army]
-
A.
branch of the United States Army
A branch of the United States Army is a specialized functional category, such as Infantry or Signal Corps, that organizes soldiers, training, and equipment around a distinct mission set and expertise area within the Army.
-
B.
component of the United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
-
C.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
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.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:11 p.m.