Triple

T10024551
Position Surface form Disambiguated ID Type / Status
Subject DoQ E200692 entity
Predicate relatedTo P37 FINISHED
Object DNS over TLS E200693 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: DNS over TLS | Statement: [DoQ, relatedTo, DNS over TLS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DNS over TLS
Context triple: [DoQ, relatedTo, DNS over TLS]
  • A. DNS over TLS chosen
    DNS over TLS is a security protocol that encrypts traditional DNS queries and responses using Transport Layer Security to protect user privacy and prevent eavesdropping or tampering.
  • B. 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.
  • C. DNS over HTTPS
    DNS over HTTPS is a protocol that sends DNS queries and responses over encrypted HTTPS connections to enhance privacy and security.
  • D. DNSCrypt
    DNSCrypt is a security protocol that authenticates and encrypts DNS traffic between a user’s device and a DNS resolver to prevent spying, spoofing, and tampering.
  • E. DNS over QUIC (DoQ)
    DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
  • 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_69ca831c45f08190ac1505cc15076608 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd7d9c9c81909a0a0917deed0973 completed April 2, 2026, 1:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69d28222773c81908eb84974fd6ce106 completed April 5, 2026, 3:39 p.m.
Created at: March 30, 2026, 8:53 p.m.