Triple
T9807786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Remote Sensing Policy Act of 1992 |
E238195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | remote sensing law |
C26878
|
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: remote sensing law Context triple: [Land Remote Sensing Policy Act of 1992, instanceOf, remote sensing law]
-
A.
space law instrument
A space law instrument is a formal legal document—such as a treaty, agreement, or regulation—that establishes rules and principles governing activities and relationships in outer space and related celestial environments.
-
B.
intelligence law
Intelligence law is the body of legal rules, principles, and oversight mechanisms that govern the collection, analysis, sharing, and use of intelligence by state and related actors to protect national security while safeguarding rights and liberties.
-
C.
public land classification
Public land classification is the systematic categorization of government-owned lands based on their designated uses, protections, and management objectives, such as conservation, recreation, resource extraction, or development.
-
D.
land-use control
Land-use control is the set of legal and administrative mechanisms by which governments and authorities regulate how land may be developed, used, and conserved within a given jurisdiction.
-
E.
natural resources law
Natural resources law is the body of legal rules and principles governing the ownership, use, management, and conservation of natural resources such as land, water, minerals, forests, and wildlife.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.