Triple
T6432344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTLS-SRTP |
E129806
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | ZRTP |
E127265
|
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: ZRTP | Statement: [DTLS-SRTP, relatedTo, ZRTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZRTP Context triple: [DTLS-SRTP, relatedTo, ZRTP]
-
A.
ZRTP
chosen
ZRTP is a cryptographic key-agreement protocol designed to enable end-to-end encryption for real-time voice and video communications over RTP-based systems.
-
B.
Linphone
Linphone is an open-source Voice over IP (VoIP) softphone application that supports audio and video calls, messaging, and encryption across multiple platforms.
-
C.
Jitsi
Jitsi is an open-source, cross-platform suite of real-time voice, video, and chat communication tools focused on secure, encrypted conferencing.
-
D.
DTLS-SRTP
DTLS-SRTP is a security protocol framework that uses Datagram Transport Layer Security to negotiate keys and provide encryption and authentication for Secure Real-time Transport Protocol media streams, commonly used in VoIP and WebRTC.
-
E.
STUN
STUN (Session Traversal Utilities for NAT) is a network protocol that helps devices discover their public IP address and port as seen by external servers, enabling communication across NAT and firewalls.
- 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693cadf08190aca84888a3440b3d |
completed | March 22, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c640ec681881909c75a55b33c09eb6 |
completed | March 27, 2026, 8:33 a.m. |
Created at: March 22, 2026, 4:44 p.m.