Triple
T13924260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-20 |
E334821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil service pay scale |
C12388
|
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 service pay scale Context triple: [BPS-20, instanceOf, civil service pay scale]
-
A.
government pay scale system
chosen
A government pay scale system is a structured framework that defines standardized salary levels, grades, and progression rules for public sector employees based on factors such as role, seniority, qualifications, and performance.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
military pay grade
A military pay grade is a standardized classification that defines the level of compensation, rank, and seniority for service members within an armed forces pay system.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.