Triple
T13889428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-1 |
E333930
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector pay grade |
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: public sector pay grade Context triple: [BPS-1, instanceOf, public sector pay grade]
-
A.
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.
-
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.
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.
-
D.
political rank
A political rank is a hierarchical position within a governmental or political organization that defines an individual's authority, responsibilities, and status in the political system.
-
E.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.