Triple
T28397116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS DHE ciphersuites |
E719310
|
entity |
| Predicate | canUseAuthenticationAlgorithm |
P165746
|
FINISHED |
| Object | RSA |
—
|
NE NERFINISHED |
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: RSA | Statement: [TLS DHE ciphersuites, canUseAuthenticationAlgorithm, RSA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseAuthenticationAlgorithm Context triple: [TLS DHE ciphersuites, canUseAuthenticationAlgorithm, RSA]
-
A.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
usesKeyExchangeAlgorithm
Indicates that one entity employs a specific key exchange algorithm as part of establishing secure communication or cryptographic operations with another entity.
-
C.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
-
D.
hasCryptUse
Indicates that an entity makes use of cryptographic methods, protocols, or mechanisms in its operation or behavior.
-
E.
authenticationProtocol
Indicates that a particular method or set of rules is used to verify the identity of an entity before granting access or performing an action.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 28, 2026, 1:17 a.m.