Triple

T28582507
Position Surface form Disambiguated ID Type / Status
Subject PCI Software Security Framework E723413 entity
Predicate governsAssessmentType P197512 FINISHED
Object software security assessment 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: software security assessment | Statement: [PCI Software Security Framework, governsAssessmentType, software security assessment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governsAssessmentType
Context triple: [PCI Software Security Framework, governsAssessmentType, software security assessment]
  • A. typeOfAssessmentInfluenced
    Indicates that one entity has an effect on or shapes the kind of assessment applied to another entity.
  • B. typeOfAssessmentAlignment
    Indicates that an assessment is aligned with, or corresponds to, a particular standard, objective, or framework.
  • C. governsAssetType
    Indicates that one entity has authority or control over the rules, usage, or management of a particular type or class of asset.
  • D. assessmentBasis
    Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
  • E. mayBeAssessedOn
    Indicates that an entity is potentially subject to evaluation, measurement, or judgment based on another entity or criterion.
  • 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_69f01d7f92e481909847f5f3f3174a89 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69fe991bca608190b524e419642f4243 completed May 9, 2026, 2:16 a.m.
PD Predicate disambiguation batch_69fe979fc1c4819091fc48d63ea12063 completed May 9, 2026, 2:10 a.m.
PDg Predicate description generation batch_69fe991abc6c81908edbb98d61c9ca73 completed May 9, 2026, 2:16 a.m.
Created at: April 28, 2026, 4:15 a.m.