Triple
T6328688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Western Command |
E141921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Command of the Indian Army |
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: Command of the Indian Army Context triple: [South Western Command, instanceOf, Command of the Indian Army]
-
A.
Indian Army command
chosen
Indian Army command is an organizational unit responsible for directing, coordinating, and controlling military operations, administration, and logistics within a defined geographic or functional area of the Indian Army.
-
B.
Indian Army institution
An Indian Army institution is an official military establishment or organization under the Indian Army that provides training, education, research, administration, or support functions to enhance the army’s operational effectiveness and professional development.
-
C.
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.
-
D.
All India Service
All India Service is a category of elite civil services in India whose officers are recruited centrally but serve under both the central and state governments, holding key administrative, policing, and forestry positions across the country.
-
E.
Indian Army formation
An Indian Army formation is an organized military unit or grouping, such as a corps, division, brigade, or battalion, structured for command, control, and execution of land-based operations within the Indian Army.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.