Triple

T14693996
Position Surface form Disambiguated ID Type / Status
Subject Continuous At-Sea Deterrent E345105 entity
Predicate securityPrinciple P115382 FINISHED
Object continuous at-sea patrols 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: continuous at-sea patrols | Statement: [Continuous At-Sea Deterrent, securityPrinciple, continuous at-sea patrols]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityPrinciple
Context triple: [Continuous At-Sea Deterrent, securityPrinciple, continuous at-sea patrols]
  • A. securityAspect
    Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
  • B. securityAssumption
    Indicates that a particular condition, behavior, or property is presumed to hold true for security purposes within a system or protocol.
  • C. securityImplication
    Indicates that one entity has a consequence, effect, or relevance for the safety, protection, or vulnerability status of another entity or system.
  • D. securityAccess
    Indicates that one entity has permission, authorization, or the ability to access or interact with another entity in a security-controlled context.
  • E. securityRole
    Indicates that an entity holds a specific security-related role, permission level, or access profile within a system or context.
  • F. None of above. chosen

Provenance (4 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_69d822e34b348190ada4d1cdb6c7c226 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb586e7108190be644db9cf9a4d99 completed April 14, 2026, 9:45 p.m.
PD Predicate disambiguation batch_69de6579fb7881909becc8f5822b39d4 completed April 14, 2026, 4:04 p.m.
PDg Predicate description generation batch_69de716d3aac8190aaa6dc1f099b86e8 completed April 14, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:28 a.m.