Triple
T4515733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Haryana |
E102148
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government of an Indian state |
C17071
|
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 an Indian state Context triple: [Government of Haryana, instanceOf, government of an Indian state]
-
A.
government agency of India
A government agency of India is an official public-sector organization established by the Indian government to implement laws, deliver public services, regulate specific domains, and support national policies and development objectives.
-
B.
state of India
A state of India is a primary administrative and political subdivision of the country, each with its own government, legislature, and defined territorial boundaries under the Indian Constitution.
-
C.
administrative district of India
An administrative district of India is a territorial subdivision of a state or union territory, governed by district-level authorities to manage local administration, law and order, and development activities.
-
D.
Indian government agency
An Indian government agency is an official public-sector organization established by the Government of India to implement laws, deliver services, regulate specific domains, or execute policy and administrative functions at the national or regional level.
-
E.
state government office
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:02 p.m.