Triple
T9931847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curve25519-based schemes |
E192664
|
entity |
| Predicate | keyExchangeVariant |
P8663
|
FINISHED |
| Object | X25519 |
—
|
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: X25519 | Statement: [Curve25519-based schemes, keyExchangeVariant, X25519]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExchangeVariant Context triple: [Curve25519-based schemes, keyExchangeVariant, X25519]
-
A.
keyAgreement
chosen
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
-
B.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
-
C.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
D.
keyExperiment
Indicates that an experiment plays a central or pivotal role within a broader study, project, or research context.
-
E.
keyDerivation
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation process.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.