Triple
T35406257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP Low |
E1023369
|
entity |
| Predicate | controlFamilyCoverage |
P198224
|
FINISHED |
| Object | access control |
—
|
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: access control | Statement: [FedRAMP Low, controlFamilyCoverage, access control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlFamilyCoverage Context triple: [FedRAMP Low, controlFamilyCoverage, access control]
-
A.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
B.
coveringFamilyCondition
Indicates that a specified family of sets satisfies the conditions required to form a covering of a given space or structure.
-
C.
typeOfHeritageCovered
Indicates that something specifies the category or kind of heritage (e.g., cultural, natural, mixed) that is included or protected in a given context.
-
D.
providedCoverage
Indicates that one entity supplies or guarantees insurance or protective coverage to another entity or subject.
-
E.
placeCoverage
Indicates that one place geographically covers, includes, or spans the area of another place.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69fed3569ca881909f4291baeb665d9d |
completed | May 9, 2026, 6:25 a.m. |
Created at: May 3, 2026, 4:03 p.m.