Triple

T29052221
Position Surface form Disambiguated ID Type / Status
Subject Operation Resolute E735289 entity
Predicate instanceOf P0 FINISHED
Object maritime security operation C24908 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: maritime security operation
Context triple: [Operation Resolute, instanceOf, maritime security operation]
  • A. maritime security process
    A maritime security process is a coordinated set of policies, procedures, and actions designed to prevent, detect, and respond to threats and unlawful activities in maritime domains to protect vessels, ports, cargo, and maritime infrastructure.
  • B. maritime security role
    A maritime security role is a position responsible for protecting vessels, ports, and maritime infrastructure from threats such as piracy, terrorism, smuggling, and unauthorized access through surveillance, risk assessment, and enforcement measures.
  • C. maritime security infrastructure
    Maritime security infrastructure encompasses the integrated systems, facilities, technologies, and organizational frameworks designed to protect maritime domains, ports, and shipping routes from threats, ensure safe navigation, and support law enforcement and emergency response at sea.
  • D. maritime security coalition chosen
    A maritime security coalition is a collaborative alliance of nations, organizations, and agencies that coordinate resources, intelligence, and operations to protect sea lanes, deter threats, and uphold maritime law and safety.
  • E. maritime security procedure
    A maritime security procedure is a standardized set of measures and protocols designed to prevent, detect, and respond to threats or unlawful acts against ships, ports, and offshore facilities.
  • 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_69f077e64b88819094d37bdbca8191b3 completed April 28, 2026, 9:03 a.m.
Created at: April 28, 2026, 10:09 a.m.