Triple

T22309386
Position Surface form Disambiguated ID Type / Status
Subject NIST SP 800-218 E551472 entity
Predicate shortTitle P38 FINISHED
Object NIST SSDF — 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: NIST SSDF | Statement: [NIST SP 800-218, shortTitle, NIST SSDF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: NIST SSDF
Context triple: [NIST SP 800-218, shortTitle, NIST SSDF]
  • A. NIST SP 800-171
    NIST SP 800-171 is a U.S. National Institute of Standards and Technology publication that specifies security requirements for protecting Controlled Unclassified Information in non-federal information systems and organizations.
  • B. NIST SP 800-53
    NIST SP 800-53 is a widely used NIST cybersecurity standard that provides a comprehensive catalog of security and privacy controls for U.S. federal information systems and organizations.
  • C. NIST SP 800-137
    NIST SP 800-137 is a NIST cybersecurity guideline that provides a framework for implementing information security continuous monitoring (ISCM) for federal information systems and organizations.
  • D. NIST SP 800-172
    NIST SP 800-172 is a U.S. National Institute of Standards and Technology (NIST) publication that provides enhanced security requirements and controls for protecting controlled unclassified information (CUI) in high-value or high-impact federal systems and organizations.
  • E. NIST SP 800-160
    NIST SP 800-160 is a National Institute of Standards and Technology cybersecurity engineering guideline that provides systems security engineering principles and practices for developing trustworthy, secure systems.
  • 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: NIST SSDF
Target entity description: NIST SSDF is a NIST-developed framework that provides secure software development practices and guidelines to help organizations build and maintain more secure software.
  • A. NIST SP 800-171
    NIST SP 800-171 is a U.S. National Institute of Standards and Technology publication that specifies security requirements for protecting Controlled Unclassified Information in non-federal information systems and organizations.
  • B. NIST SP 800-53
    NIST SP 800-53 is a widely used NIST cybersecurity standard that provides a comprehensive catalog of security and privacy controls for U.S. federal information systems and organizations.
  • C. NIST SP 800-137
    NIST SP 800-137 is a NIST cybersecurity guideline that provides a framework for implementing information security continuous monitoring (ISCM) for federal information systems and organizations.
  • D. NIST SP 800-172
    NIST SP 800-172 is a U.S. National Institute of Standards and Technology (NIST) publication that provides enhanced security requirements and controls for protecting controlled unclassified information (CUI) in high-value or high-impact federal systems and organizations.
  • E. NIST SP 800-160
    NIST SP 800-160 is a National Institute of Standards and Technology cybersecurity engineering guideline that provides systems security engineering principles and practices for developing trustworthy, secure systems.
  • 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.