Triple
T25822371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severe Threat Level |
E650436
|
entity |
| Predicate | securityPosture |
P103633
|
FINISHED |
| Object | maximum security measures |
—
|
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: maximum security measures | Statement: [Severe Threat Level, securityPosture, maximum security measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityPosture Context triple: [Severe Threat Level, securityPosture, maximum security measures]
-
A.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
B.
securityOutcome
chosen
Indicates the result or consequence of a security-related event, measure, or decision for the involved entities.
-
C.
securityAttention
Indicates that an entity is the focus of monitoring, concern, or scrutiny from a security perspective.
-
D.
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.
-
E.
securityAdvisory
Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 7:30 a.m.