Triple
T5768042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTLS |
E127260
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | DTLS 1.3 |
E127260
|
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: DTLS 1.3 | Statement: [DTLS, hasVersion, DTLS 1.3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DTLS 1.3 Context triple: [DTLS, hasVersion, DTLS 1.3]
-
A.
DTLS
chosen
DTLS (Datagram Transport Layer Security) is a protocol that provides TLS-like encryption, integrity, and authentication for datagram-based communications such as UDP.
-
B.
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.
-
C.
DNS over DTLS
DNS over DTLS is a protocol that secures DNS queries using Datagram Transport Layer Security over UDP, providing encryption and integrity while preserving DNS’s low-latency, connectionless nature.
-
D.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
E.
QUIC TLS usage specification
The QUIC TLS usage specification is an IETF document that defines how the QUIC transport protocol integrates and uses TLS for secure, encrypted internet communication.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029731adc8190888adc8178a08e90 |
completed | March 22, 2026, 5:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a16ea7108190adb0756dac94c42c |
completed | March 23, 2026, 2:11 a.m. |
Created at: March 22, 2026, 3:49 p.m.