Triple
T31928258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra Land Revenue Code |
E815171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian state statute |
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: Indian state statute Context triple: [Maharashtra Land Revenue Code, instanceOf, Indian state statute]
-
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.
United States state law
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
-
C.
internal statute
An internal statute is a formal, binding rule or regulation adopted within an organization to govern its internal operations, decision-making processes, and member conduct.
-
D.
Act of the Uttar Pradesh Legislature
An Act of the Uttar Pradesh Legislature is a formal law enacted by the legislative body of the state of Uttar Pradesh that establishes, amends, or repeals legal provisions applicable within the state's jurisdiction.
-
E.
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.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:04 a.m.