Triple
T18268810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infantry Directorate |
E437554
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Army directorate |
C15089
|
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 directorate Context triple: [Infantry Directorate, instanceOf, Indian Army directorate]
-
A.
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.
-
B.
Indian Army institution
chosen
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.
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.
-
D.
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.
-
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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.