Triple
T35406157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP High impact level |
E1023367
|
entity |
| Predicate | usesControlBaselineFrom |
P55279
|
FINISHED |
| Object | NIST SP 800-53 |
—
|
NE NERFINISHED |
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: NIST SP 800-53 | Statement: [FedRAMP High impact level, usesControlBaselineFrom, NIST SP 800-53]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlBaselineFrom Context triple: [FedRAMP High impact level, usesControlBaselineFrom, NIST SP 800-53]
-
A.
usesBaseline
chosen
Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
-
B.
controlBasis
Indicates that one entity serves as the foundational source or basis for another entity’s control or governance over something.
-
C.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
D.
controlBaselineSize
Indicates that one entity regulates or sets the standard reference size against which other sizes or variations are measured.
-
E.
usesBasePoint
Indicates that one entity performs an operation or defines a structure by referencing or relying on a specific base point.
- 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_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:03 p.m.