Triple
T38373130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encrypted Client Hello |
E893544
|
entity |
| Predicate | leavesUnencrypted |
P190811
|
FINISHED |
| Object | outer ClientHello |
—
|
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: outer ClientHello | Statement: [Encrypted Client Hello, leavesUnencrypted, outer ClientHello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leavesUnencrypted Context triple: [Encrypted Client Hello, leavesUnencrypted, outer ClientHello]
-
A.
dataIsEncrypted
Indicates that the referenced data is stored or transmitted in an encrypted form rather than in plaintext.
-
B.
requiresEncryption
Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
-
C.
randomizedEncryptionDisallows
Indicates that the use of randomized encryption prevents or forbids a particular operation, property, or type of access from being possible.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
encryptionByDefault
Indicates that data is automatically encrypted without requiring any manual configuration or action by the involved parties.
- F. None of above. chosen
Provenance (4 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.