Triple
T2277135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21 SAS |
E51195
|
entity |
| Predicate | operationalSecurity |
P3815
|
FINISHED |
| Object | many activities are classified |
—
|
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: many activities are classified | Statement: [21 SAS, operationalSecurity, many activities are classified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalSecurity Context triple: [21 SAS, operationalSecurity, many activities are classified]
-
A.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
-
B.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
C.
securityAspect
chosen
Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
-
D.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
E.
securityEnvironment
Indicates the overall conditions, threats, and protective measures that characterize the safety and risk context in which an entity operates.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc1ee22988190b7fa28b0b62e8668 |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.