Triple
T18268694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Director General of Manpower Planning and Personnel Services |
E437551
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior Indian Army appointment |
C2499
|
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: senior Indian Army appointment Context triple: [Director General of Manpower Planning and Personnel Services, instanceOf, senior Indian Army appointment]
-
A.
military appointment
chosen
A military appointment is an official position or duty assigned to a service member within the armed forces, defining their role, responsibilities, and authority.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Indian Army recruitment program
The Indian Army recruitment program is a structured, nationwide system for attracting, evaluating, and enlisting eligible candidates into various branches and roles of the Indian Army through standardized examinations, physical tests, and medical assessments.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.