Triple
T25334192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam Forest Regulation, 1891 |
E635231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian environmental 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 environmental statute Context triple: [Assam Forest Regulation, 1891, instanceOf, Indian environmental 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.
environmental protection legislation
Environmental protection legislation comprises the body of laws and regulations designed to prevent, reduce, and remediate harm to the natural environment by controlling human activities and managing natural resources sustainably.
-
C.
environmental law journal
An environmental law journal is a scholarly periodical that publishes articles, case notes, and commentary analyzing legal issues, policies, and developments related to environmental protection and natural resources.
-
D.
environmental law doctrine
A body of legal principles and theories that guide the interpretation, application, and development of laws aimed at protecting the environment and regulating human impacts on natural resources.
-
E.
environmental regulation compilation
A curated collection of laws, policies, standards, and guidelines that govern human impacts on the environment, organized for reference, analysis, and compliance support.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:32 p.m.