Triple
T23488418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AGMUT cadre |
E570604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | All India Services cadre |
C4236
|
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: All India Services cadre Context triple: [AGMUT cadre, instanceOf, All India Services cadre]
-
A.
All India Service
chosen
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.
-
B.
civil service cadre
A civil service cadre is a structured group of professional government officials organized by rank, function, and career path to implement public policies and administer state affairs.
-
C.
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.
-
D.
Chief of Army Staff of India
The Chief of Army Staff of India is the professional head and highest-ranking officer of the Indian Army, responsible for its command, operational readiness, and overall administration under the authority of the Government of India.
-
E.
government position in India
A government position in India is an official role within the country's public sector institutions, responsible for implementing laws, policies, and administrative functions at the central, state, or local levels.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:04 p.m.