Triple

T13106379
Position Surface form Disambiguated ID Type / Status
Subject FedRAMP Moderate E310853 entity
Predicate dataSensitivity P406 FINISHED
Object sensitive but unclassified data 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: sensitive but unclassified data | Statement: [FedRAMP Moderate, dataSensitivity, sensitive but unclassified data]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataSensitivity
Context triple: [FedRAMP Moderate, dataSensitivity, sensitive but unclassified data]
  • A. dataSegregation
    Indicates that data is kept separate or partitioned so that information from one group, context, or user is not mixed or accessible with that of another.
  • B. securityClassification chosen
    Indicates the level or category of security sensitivity or access restriction assigned to an entity.
  • C. disclosureLevel
    Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
  • D. sensitivityFeature
    Indicates a relationship where one entity functions as a sensitivity-related characteristic, parameter, or attribute of another entity.
  • E. privacyCharacteristic
    Indicates the specific privacy-related property or feature that characterizes how information is handled, protected, or exposed in a given context.
  • 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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98154c9f48190aeca779d97151759 completed April 10, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69d98041a3548190a05ddd83dbb660fa completed April 10, 2026, 10:57 p.m.
Created at: April 9, 2026, 9:05 p.m.