Triple
T13889112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of India service rules |
E333923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil service regulation framework |
C11529
|
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 regulation framework Context triple: [Government of India service rules, instanceOf, civil service regulation framework]
-
A.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
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.
federal government framework
A federal government framework is a structural system that defines how power, responsibilities, and relationships are distributed and coordinated between a central authority and its constituent regional or state governments.
-
D.
central government regulations
Central government regulations are legally binding rules and standards issued by national authorities to direct, control, and coordinate activities within a country in accordance with public policy and law.
-
E.
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.
- 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.