Triple
T35406243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP Low |
E1023369
|
entity |
| Predicate | securityImpactLevel |
P108088
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [FedRAMP Low, securityImpactLevel, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityImpactLevel Context triple: [FedRAMP Low, securityImpactLevel, low]
-
A.
impactLevel
chosen
Indicates the degree or intensity of effect that one entity, action, or event has on another.
-
B.
securityImplication
Indicates that one entity has a consequence, effect, or relevance for the safety, protection, or vulnerability status of another entity or system.
-
C.
integrityImpact
Indicates the extent to which the relationship or action compromises, alters, or destroys the accuracy, consistency, or trustworthiness of the affected entity’s information or state.
-
D.
securityChallengesImpact
Indicates how security-related challenges affect or influence a given system, process, or outcome.
-
E.
securityPriority
Indicates the relative level of importance or urgency assigned to security-related actions, issues, or protections in comparison to other concerns.
- 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_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:03 p.m.