Triple
T21582305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIPS 200 |
E532550
|
entity |
| Predicate | securityAreasCovered |
P89715
|
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: [FIPS 200, securityAreasCovered, access control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityAreasCovered Context triple: [FIPS 200, securityAreasCovered, access control]
-
A.
securityTypeCoverage
chosen
Indicates the type or category of security that is covered or included under a given coverage or policy.
-
B.
securityArrangementsBy
Indicates that one entity is responsible for providing, organizing, or overseeing security arrangements for another entity or situation.
-
C.
sectorProtected
Indicates that a particular sector or area is safeguarded from harm, access, or exploitation by some form of protection or regulation.
-
D.
securityLocation
Indicates the place or area where security-related activities, measures, or responsibilities are situated or applied.
-
E.
securityArrangements
Indicates the existence, nature, or details of protective measures or safeguards established between or around entities.
- 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.