Triple
T18873720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hague-Visby Rules |
E461631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | carriage of goods by sea regime |
C41427
|
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: carriage of goods by sea regime Context triple: [Hague-Visby Rules, instanceOf, carriage of goods by sea regime]
-
A.
maritime transport document
A maritime transport document is an official record, such as a bill of lading or sea waybill, that evidences the contract of carriage of goods by sea, acknowledges receipt of the cargo, and may confer rights to claim delivery.
-
B.
maritime transport company
A maritime transport company is an organization that operates ships and related logistics to move cargo and/or passengers across seas and oceans between ports.
-
C.
International Maritime Organization instrument
An International Maritime Organization instrument is a formal legal or regulatory document—such as a convention, code, or guideline—adopted by the IMO to establish international standards for maritime safety, security, and environmental protection.
-
D.
maritime cargo terminal
A maritime cargo terminal is a specialized facility at a seaport where ships are loaded and unloaded, and cargo is temporarily stored, sorted, and transferred between sea and land transportation modes.
-
E.
marine transit service
A marine transit service is an organized operation that transports passengers and/or cargo over water using vessels such as ferries, ships, or boats along scheduled or on-demand routes.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:57 a.m.