Triple
T4132992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Western Command (India) |
E85083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Army command |
C14993
|
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: Indian Army command Context triple: [South Western Command (India), instanceOf, Indian Army command]
-
A.
Indian Army position
An Indian Army position is a specific rank or role within the organizational hierarchy of the Indian Army, defining an individual's authority, responsibilities, and duties in military operations and administration.
-
B.
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.
-
C.
army commander post
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
-
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.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
- F. None of above. chosen
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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:42 p.m.