Triple
T23488389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIS |
E570603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil services cadre system |
C34320
|
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: civil services cadre system Context triple: [AIS, instanceOf, civil services cadre system]
-
A.
civil service cadre
chosen
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.
-
B.
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.
-
C.
civil service grading system
A civil service grading system is a structured framework that categorizes public sector jobs and employees into standardized grades or levels based on responsibilities, qualifications, and pay scales to ensure fairness, transparency, and consistency in employment and promotion.
-
D.
civil service code
A civil service code is a formal set of rules and principles that governs the conduct, responsibilities, and standards of behavior for public sector employees.
-
E.
specialized civil service
A specialized civil service is a segment of the public administration composed of professionals with specific technical or sectoral expertise who perform defined governmental functions under merit-based rules and career structures.
- 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.