Triple
T35406252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP Low |
E1023369
|
entity |
| Predicate | informationSensitivity |
P406
|
FINISHED |
| Object | least sensitive federal information |
—
|
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: least sensitive federal information | Statement: [FedRAMP Low, informationSensitivity, least sensitive federal information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationSensitivity Context triple: [FedRAMP Low, informationSensitivity, least sensitive federal information]
-
A.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
C.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
D.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
E.
securityGranularity
Indicates the level of detail or specificity at which security controls, permissions, or protections are defined and applied within a system or 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7956353fc8190a54e35f018f4171f |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.