Triple

T22309400
Position Surface form Disambiguated ID Type / Status
Subject NIST SP 800-218 E551472 entity
Predicate provides P490 FINISHED
Object Secure Software Development Framework — NE NERFINISHED

How this triple was built (3 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: Secure Software Development Framework | Statement: [NIST SP 800-218, provides, Secure Software Development Framework]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Secure Software Development Framework
Context triple: [NIST SP 800-218, provides, Secure Software Development Framework]
  • A. Security framework
    The Security framework is an Apple software library that provides APIs for managing cryptography, keychains, certificates, and secure authentication on macOS and other Apple platforms.
  • B. PCI Software Security Framework
    The PCI Software Security Framework is a set of standards and validation programs from the PCI Security Standards Council that define modern security requirements and lifecycle practices for payment software to protect cardholder data.
  • C. SAFE Framework of Standards
    The SAFE Framework of Standards is a global customs security and trade facilitation framework that sets guidelines for securing and streamlining international supply chains.
  • D. Verified Software Toolchain
    Verified Software Toolchain is a formally verified compiler infrastructure for the C programming language that uses the Coq proof assistant to ensure end-to-end correctness of compiled programs.
  • E. PCI Secure Software Lifecycle Standard
    The PCI Secure Software Lifecycle Standard is a PCI Security Standards Council framework that defines security requirements and best practices for developing and maintaining payment software securely throughout its entire lifecycle.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Secure Software Development Framework
Target entity description: The Secure Software Development Framework is a NIST-guided set of best practices and processes for building, deploying, and maintaining software with security integrated throughout its lifecycle.
  • A. Security framework
    The Security framework is an Apple software library that provides APIs for managing cryptography, keychains, certificates, and secure authentication on macOS and other Apple platforms.
  • B. PCI Software Security Framework
    The PCI Software Security Framework is a set of standards and validation programs from the PCI Security Standards Council that define modern security requirements and lifecycle practices for payment software to protect cardholder data.
  • C. SAFE Framework of Standards
    The SAFE Framework of Standards is a global customs security and trade facilitation framework that sets guidelines for securing and streamlining international supply chains.
  • D. Verified Software Toolchain
    Verified Software Toolchain is a formally verified compiler infrastructure for the C programming language that uses the Coq proof assistant to ensure end-to-end correctness of compiled programs.
  • E. PCI Secure Software Lifecycle Standard
    The PCI Secure Software Lifecycle Standard is a PCI Security Standards Council framework that defines security requirements and best practices for developing and maintaining payment software securely throughout its entire lifecycle.
  • F. None of above. chosen

Provenance (2 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_69e11e46c0188190800181a4233f28fe completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1574d53148190a1ec07f849e1ae9d completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.