Triple
T21582449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-53 |
E532553
|
entity |
| Predicate | organizesControlsBy |
P5709
|
FINISHED |
| Object | control families |
—
|
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: control families | Statement: [NIST SP 800-53, organizesControlsBy, control families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesControlsBy Context triple: [NIST SP 800-53, organizesControlsBy, control families]
-
A.
organizesInto
chosen
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
-
B.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
C.
organizingElement
Indicates that one entity serves as the primary structuring or coordinating element that arranges, orders, or systematizes other related entities or components.
-
D.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
E.
allocatesControlTo
Indicates that decision-making authority or control over something is assigned or transferred from one entity to another.
- 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_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_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.