Triple
T21582450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-53 |
E532553
|
entity |
| Predicate | controlFamilyExample |
P144050
|
FINISHED |
| Object | Access Control (AC) |
—
|
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 (AC) | Statement: [NIST SP 800-53, controlFamilyExample, Access Control (AC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlFamilyExample Context triple: [NIST SP 800-53, controlFamilyExample, Access Control (AC)]
-
A.
coreFamily
Indicates that one entity belongs to the other’s immediate (nuclear) family, such as parent, child, or sibling.
-
B.
familyControlled
Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
-
C.
targetsFamilyOf
Indicates that one entity is directed against, aimed at, or designed to affect a particular family or group of closely related entities.
-
D.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
E.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5d28e08190a38de7ad7ed12743 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:31 p.m.