Triple
T21998868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Financial Rules |
E543273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Government of India rules |
C12062
|
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: Government of India rules Context triple: [General Financial Rules, instanceOf, Government of India rules]
-
A.
Indian regulation
chosen
Indian regulation refers to the body of laws, rules, and guidelines enacted by Indian legislative, executive, and regulatory authorities to govern economic, social, and administrative activities within the country.
-
B.
Act of Parliament of India
An Act of Parliament of India is a formal written law enacted by the Indian Parliament through its legislative process, which becomes legally binding upon receiving presidential assent and publication.
-
C.
Indian band government
An Indian band government is the local governing authority of a First Nations band in Canada, responsible for administering band affairs, managing community services and resources, and representing its members in dealings with other governments.
-
D.
government of an Indian state
The government of an Indian state is the political and administrative authority responsible for governing that state, comprising the Governor, the elected legislative assembly, and the council of ministers headed by the Chief Minister.
-
E.
Indian government program
An Indian government program is an organized initiative launched and funded by the Government of India to address specific social, economic, or developmental objectives through targeted policies, schemes, and services.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:19 p.m.