Triple
T22064797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Information Service |
E545239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Group A civil service |
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: Group A civil service Context triple: [Indian Information Service, instanceOf, Group A civil service]
-
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.
federal civil service
The federal civil service is the body of non-military government employees who are hired and promoted based on merit to administer and implement the policies, programs, and day-to-day operations of the federal government.
-
C.
state civil service
State civil service is the organized body of government employees at the state level who are hired and managed under merit-based rules to administer public programs and implement state policies.
-
D.
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.
-
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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.