Triple

T29503817
Position Surface form Disambiguated ID Type / Status
Subject Basic E748454 entity
Predicate securityBestPractice P11328 FINISHED
Object combine with HTTPS and strong password policies 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: combine with HTTPS and strong password policies | Statement: [Basic, securityBestPractice, combine with HTTPS and strong password policies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityBestPractice
Context triple: [Basic, securityBestPractice, combine with HTTPS and strong password policies]
  • A. securityRecommendation chosen
    Indicates that one entity advises or prescribes specific security-related actions, settings, or measures for another entity.
  • B. securityPracticeIncludes
    Indicates that a broader security practice encompasses, contains, or makes use of a specific security measure, control, or activity.
  • C. securityAdvisory
    Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
  • D. securityPrinciple
    Indicates that an entity embodies, defines, or is governed by a fundamental rule, guideline, or concept related to security.
  • E. securityProgram
    Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
  • 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_69f0bd455a9c8190b40a3e8ea38cf61f completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f7221dc9a88190bb8194fcc29c42bc completed May 3, 2026, 10:23 a.m.
PD Predicate disambiguation batch_69f72153a9188190b02adc84e1be4af8 completed May 3, 2026, 10:20 a.m.
Created at: April 28, 2026, 4:26 p.m.