Triple
T24328373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port and Harbor Law of Japan |
E613165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | port and harbor law |
C14237
|
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: port and harbor law Context triple: [Port and Harbor Law of Japan, instanceOf, port and harbor law]
-
A.
port governance legislation
chosen
Port governance legislation comprises the legal frameworks and regulatory instruments that define the ownership, management structures, operational rules, and oversight mechanisms for the administration and development of seaports.
-
B.
navigation law
Navigation law is a legal framework governing the rights, responsibilities, and regulations related to the movement of vessels, aircraft, or vehicles through maritime, air, or other navigable spaces.
-
C.
maritime law enforcement activity
Maritime law enforcement activity is the set of actions by authorized agencies to monitor, control, and ensure compliance with laws and regulations in maritime zones, including preventing and responding to illegal activities at sea.
-
D.
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.
-
E.
maritime jurisdictional office
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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:54 a.m.