Triple
T17463809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queensland maritime safety authorities |
E425224
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime safety regulator |
C18354
|
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: maritime safety regulator Context triple: [Queensland maritime safety authorities, instanceOf, maritime safety regulator]
-
A.
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.
-
B.
maritime navigation authority
A maritime navigation authority is an organization responsible for regulating, managing, and ensuring the safety and efficiency of vessel movements and navigational systems within designated waters.
-
C.
marine accident investigation body
A marine accident investigation body is an independent authority responsible for examining maritime incidents to determine causes, identify safety issues, and recommend measures to prevent future occurrences.
-
D.
maritime safety certificate
A maritime safety certificate is an official document issued by a competent authority confirming that a vessel complies with required safety regulations and standards for operation at sea.
-
E.
maritime jurisdictional office
chosen
A maritime jurisdictional office is a governmental or regulatory entity responsible for overseeing, enforcing, and administering laws, regulations, and policies within a defined maritime area or coastal zone.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.