Triple
T33926560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E869766
|
entity |
| Predicate | definesForProtocolLayer |
P11823
|
FINISHED |
| Object | SSH Transport Layer Protocol |
—
|
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: SSH Transport Layer Protocol | Statement: [RFC 6668, definesForProtocolLayer, SSH Transport Layer Protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesForProtocolLayer Context triple: [RFC 6668, definesForProtocolLayer, SSH Transport Layer Protocol]
-
A.
definesApplicationLayerProtocol
Indicates that an entity specifies or determines which application-layer communication protocol is used by another entity or interaction.
-
B.
protocolLayer
chosen
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
-
C.
definesInterfaceProtocol
Indicates that one entity specifies or establishes the communication or interaction protocol that another entity must follow as its interface.
-
D.
protocolDefined
Indicates that a specific protocol formally specifies or governs the behavior, format, or interaction associated with the related entities.
-
E.
specifiesProtocolExtensionFor
Indicates that one protocol extension defines or constrains the behavior, capabilities, or usage of another protocol.
- 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_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 1, 2026, 1:49 a.m.