Triple
T20794838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 99-198 |
E511884
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | omnibus agricultural law |
C15167
|
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: omnibus agricultural law Context triple: [Public Law 99-198, instanceOf, omnibus agricultural law]
-
A.
agricultural law
chosen
Agricultural law is the body of legal rules, regulations, and policies that govern farming activities, food production, land use, environmental impacts, and the rights and obligations of agricultural producers and related stakeholders.
-
B.
agricultural policy regime
An agricultural policy regime is the structured set of laws, institutions, incentives, and practices through which a government shapes agricultural production, markets, land use, and rural livelihoods over time.
-
C.
agrarian reform
Agrarian reform is the deliberate reorganization of agricultural land ownership, tenure, and support systems to improve equity, productivity, and rural livelihoods.
-
D.
agricultural fund
An agricultural fund is an investment vehicle that pools capital to invest in agriculture-related assets such as farmland, agribusiness companies, commodities, or agricultural infrastructure to generate returns linked to the agricultural sector.
-
E.
agriculture policy coordination body
An agriculture policy coordination body is an organization responsible for aligning, harmonizing, and overseeing agricultural policies and programs across relevant government agencies and stakeholders to achieve coherent, sustainable, and effective sector outcomes.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:39 p.m.