Triple
T18268449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Secretary’s Branch |
E437545
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of the Indian Army |
C39977
|
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: administrative division of the Indian Army Context triple: [Military Secretary’s Branch, instanceOf, administrative division of the Indian Army]
-
A.
branch of the Indian Army
A branch of the Indian Army is a major organizational subdivision responsible for specific operational, combat, or support functions within the Army’s overall structure.
-
B.
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.
-
C.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
D.
Indian Army command
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.
-
E.
Indian Armed Forces formation
An Indian Armed Forces formation is an organized military unit or grouping, such as a command, corps, division, brigade, or equivalent structure, established to plan, coordinate, and conduct operations within the Indian Army, Navy, or Air Force.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.