Triple
T11216211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenSSH |
E265444
|
entity |
| Predicate | supportsKeyType |
P9247
|
FINISHED |
| Object | Ed25519 |
E192669
|
NE 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: Ed25519 | Statement: [OpenSSH, supportsKeyType, Ed25519]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ed25519 Context triple: [OpenSSH, supportsKeyType, Ed25519]
-
A.
Ed25519
chosen
Ed25519 is a high-speed, high-security elliptic-curve digital signature scheme widely used in modern cryptographic protocols and software.
-
B.
EdDSA
EdDSA (Edwards-curve Digital Signature Algorithm) is a modern public-key signature scheme designed for high performance, security, and resistance to side-channel attacks, commonly used with curves like Ed25519.
-
C.
Ed448
Ed448 is a modern high-security elliptic-curve digital signature algorithm designed for strong cryptographic assurance and efficient performance.
-
D.
NIST P-256 family
The NIST P-256 family is a widely used set of 256-bit elliptic curves standardized by NIST for secure public-key cryptography and digital signatures.
-
E.
secp256k1
secp256k1 is a widely used elliptic curve defined over a 256-bit prime field, best known as the cryptographic foundation for Bitcoin and several other blockchain systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69e49762e3188190ba3c0e01cf04f6a1 |
completed | April 19, 2026, 8:50 a.m. |
Created at: April 8, 2026, 9:30 p.m.