Triple
T33926568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E869766
|
entity |
| Predicate | protocolNegotiationMechanism |
P34326
|
FINISHED |
| Object | SSH key exchange algorithm negotiation |
—
|
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: SSH key exchange algorithm negotiation | Statement: [RFC 6668, protocolNegotiationMechanism, SSH key exchange algorithm negotiation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolNegotiationMechanism Context triple: [RFC 6668, protocolNegotiationMechanism, SSH key exchange algorithm negotiation]
-
A.
negotiatesProtocolUsing
Indicates that one entity establishes or conducts a negotiation process with another entity using a specified protocol as the communication or agreement mechanism.
-
B.
negotiationMechanism
chosen
Indicates a process or method through which parties communicate and bargain to reach a mutually acceptable agreement.
-
C.
protocolDiscussed
Indicates that a protocol has been reviewed and talked through between relevant parties.
-
D.
protocolUse
Indicates that an entity employs or relies on a specific protocol to perform a communication, interaction, or operation.
-
E.
protocolName
Indicates the specific communication or interaction protocol used or associated with an entity or connection.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.