Triple
T12588063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jharkhand Legislative Assembly |
E300519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state assembly of India |
C32190
|
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: state assembly of India Context triple: [Jharkhand Legislative Assembly, instanceOf, state assembly of India]
-
A.
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.
-
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.
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.
-
D.
session of Parliament of India
A session of Parliament of India is a formally convened period during which the Lok Sabha and/or Rajya Sabha meet to conduct legislative business, including debating, amending, and passing laws, as well as overseeing the executive.
-
E.
Andhra Pradesh Legislative Assembly constituency
An Andhra Pradesh Legislative Assembly constituency is a geographically defined electoral division within the Indian state of Andhra Pradesh that elects one member to the Andhra Pradesh Legislative Assembly.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:05 p.m.