Triple
T11216209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenSSH |
E265444
|
entity |
| Predicate | supportsKeyExchangeAlgorithm |
P42730
|
FINISHED |
| Object | curve25519-sha256 |
—
|
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: curve25519-sha256 | Statement: [OpenSSH, supportsKeyExchangeAlgorithm, curve25519-sha256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeyExchangeAlgorithm Context triple: [OpenSSH, supportsKeyExchangeAlgorithm, curve25519-sha256]
-
A.
hasKeyAgreement
chosen
Indicates that two parties share or have established a cryptographic key agreement used to securely derive a common secret key.
-
B.
supportsCipherSuite
Indicates that one entity is capable of using or handling a specified cryptographic cipher suite in secure communications.
-
C.
supportsKeyManagementProtocol
Indicates that one entity is capable of using or is compatible with a specified key management protocol for handling cryptographic keys.
-
D.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.