Triple

T33007005
Position Surface form Disambiguated ID Type / Status
Subject CLdN RoRo E844529 entity
Predicate hasRegulatoryCompliance GENERATED
Object IMO regulations UNRECOGNIZED GENERATED

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegulatoryCompliance
Context triple: [CLdN RoRo, hasRegulatoryCompliance, IMO regulations]
  • A. hasRegulations chosen
    Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
  • B. hasSafetyRegulationCompliance
    Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
  • C. regulatesComplianceWith
    Indicates that one entity oversees, enforces, or sets rules to ensure another entity adheres to specified standards, laws, or requirements.
  • D. hasRegulatoryApproval
    Indicates that an entity has received formal authorization or clearance from a relevant regulatory authority to operate, be sold, or be used in a specified context.
  • E. appliesRegulatoryStandard
    Indicates that one entity enforces or uses a specific regulatory standard in relation to another entity or context.
  • 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_69f3494e59f08190b9127c693e5c7e8f completed April 30, 2026, 12:21 p.m.
Created at: May 1, 2026, 1:23 a.m.