Triple
T1711762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS 1.2 Finished message |
E37197
|
entity |
| Predicate | hasSecurityGoal |
P10168
|
FINISHED |
| Object | mutual assurance of handshake consistency |
—
|
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: mutual assurance of handshake consistency | Statement: [TLS 1.2 Finished message, hasSecurityGoal, mutual assurance of handshake consistency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityGoal Context triple: [TLS 1.2 Finished message, hasSecurityGoal, mutual assurance of handshake consistency]
-
A.
securityGoal
chosen
Indicates that an action, system, or policy is intended to achieve, support, or satisfy a specified security objective or protection target.
-
B.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
C.
hasPolicyGoal
Indicates that an entity is associated with, or aims to achieve, a specific policy objective or target.
-
D.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
E.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.