Triple

T2967399
Position Surface form Disambiguated ID Type / Status
Subject M/V Aurora E80196 entity
Predicate safetyRegime P17338 FINISHED
Object U.S. Coast Guard inspected vessel LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: U.S. Coast Guard inspected vessel | Statement: [M/V Aurora, safetyRegime, U.S. Coast Guard inspected vessel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: safetyRegime
Context triple: [M/V Aurora, safetyRegime, U.S. Coast Guard inspected vessel]
  • A. safetyRegulationEffect
    Indicates how a safety regulation influences or changes the conditions, behaviors, or outcomes associated with the regulated entities.
  • B. hasSafetyRegulationCompliance chosen
    Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
  • C. safetyRequirement
    Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
  • D. safety
    Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
  • E. safetyGoal
    Indicates that an entity is associated with a specific safety objective or target condition intended to prevent harm or reduce risk.
  • F. None of above.

Provenance (3 batches)

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_69ad8b14ffe881908ffed62f9595c867 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad996fa4388190abd319c69ee583d9 completed March 8, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69ad960e71f8819088179d11248c6ed0 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:58 p.m.