Triple
T13889380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS |
E333929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector grading structure |
C12389
|
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 grading structure Context triple: [BPS, instanceOf, public sector grading structure]
-
A.
civil service grading system
chosen
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.
-
B.
public sector investment schedule
A public sector investment schedule is a planned timeline and allocation of government capital expenditures across projects and sectors to achieve specified policy, economic, and social objectives.
-
C.
agricultural grading standard
An agricultural grading standard is a formalized set of criteria and specifications used to classify and evaluate the quality, size, condition, and other attributes of agricultural products for trade and regulatory purposes.
-
D.
classification board
A classification board is an authoritative body or panel that evaluates and assigns categories, ratings, or classifications to items such as media, products, or information based on defined criteria and standards.
-
E.
climbing grade system
A climbing grade system is a standardized scale used to describe the difficulty, technical demands, and sometimes risk level of climbing routes or boulder problems.
- 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.