Triple
T23147438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Railway Protection Force Service |
E578230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Group ‘A’ civil service |
C45638
|
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 Railway Protection Force Service, instanceOf, Group ‘A’ civil service]
-
A.
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.
-
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.
Group A service
chosen
Group A service is a category of offerings that provide specialized support or functionality to a defined set of users or systems within a broader service ecosystem.
-
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.
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.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:01 p.m.