Triple
T7097356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirección General de Territorio Marítimo y Marina Mercante de Chile |
E165365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autoridad marítima |
C4267
|
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: autoridad marítima Context triple: [Dirección General de Territorio Marítimo y Marina Mercante de Chile, instanceOf, autoridad marítima]
-
A.
maritime navigation authority
chosen
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.
-
B.
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.
-
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 passage
A maritime passage is a navigable sea route or waterway that connects larger bodies of water, enabling the movement of ships and maritime traffic between regions.
-
E.
maritime designation
A maritime designation is a formal label or classification assigned to ships, sea areas, routes, or maritime activities to define their status, function, or regulatory conditions.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:41 p.m.