Triple
T36854688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Estate Management Act 2014 (NSW) |
E910762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marine management legislation |
C51424
|
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: marine management legislation Context triple: [Marine Estate Management Act 2014 (NSW), instanceOf, marine management legislation]
-
A.
marine policy framework
A marine policy framework is a structured set of principles, regulations, and governance mechanisms that guide the sustainable use, management, and protection of ocean and coastal resources.
-
B.
maritime safety regulation
Maritime safety regulation is the body of laws, standards, and procedures designed to prevent accidents, protect life, property, and the marine environment, and ensure safe operations in maritime activities.
-
C.
marine pollution control regime
A marine pollution control regime is an integrated set of laws, institutions, policies, and enforcement mechanisms designed to prevent, reduce, and manage pollution in marine environments from various human activities.
-
D.
coastal management law
chosen
Coastal management law is the body of legal rules, policies, and regulations that govern the use, protection, and development of coastal zones to balance environmental conservation, economic activities, and community interests.
-
E.
naval legislation
Naval legislation comprises the body of laws, regulations, and international agreements that govern the operation, safety, security, and environmental impact of ships and maritime activities at sea and in ports.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.