Triple
T6127167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Police Service (Recruitment) Rules |
E136622
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | central government regulations |
C19975
|
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: central government regulations Context triple: [Indian Police Service (Recruitment) Rules, instanceOf, central government regulations]
-
A.
central government
The central government is the primary national authority that exercises overarching political, legislative, and administrative control over a state, coordinating and regulating functions that affect the country as a whole.
-
B.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
C.
national government
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
-
D.
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.
-
E.
federal law
A federal law is a legally binding rule or statute enacted by a national government’s legislative body that applies uniformly across all states or regions within that nation.
- F. None of above. chosen
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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.