Triple
T32502025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omnibus Public Land Management Act of 2009 |
E830686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public lands legislation |
C61557
|
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: public lands legislation Context triple: [Omnibus Public Land Management Act of 2009, instanceOf, public lands legislation]
-
A.
public lands
Public lands are areas of land and natural resources owned collectively by the public and managed by government agencies for purposes such as conservation, recreation, resource extraction, and cultural or historical preservation.
-
B.
public service legislation
Public service legislation comprises the body of laws and regulations that establish, organize, and govern the duties, standards, and operations of government services and public sector employees.
-
C.
regional legislation
Regional legislation comprises the laws, regulations, and legal frameworks enacted by subnational authorities (such as states, provinces, or regions) to govern matters within their territorial jurisdiction.
-
D.
canonical legislation
Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
-
E.
court legislation
Court legislation encompasses the body of laws, rules, and legal principles established or interpreted by courts that govern judicial processes and influence the application of statutory and constitutional provisions.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.