Triple

T8621506
Position Surface form Disambiguated ID Type / Status
Subject RFC 9250 E204175 entity
Predicate specifiesProtocol P12564 FINISHED
Object DNS over QUIC E40276 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 QUIC | Statement: [RFC 9250, specifiesProtocol, DNS over QUIC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DNS over QUIC
Context triple: [RFC 9250, specifiesProtocol, DNS over QUIC]
  • A. DNS over QUIC (DoQ) chosen
    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.
  • 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. DNS over TLS
    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.
  • E. QUIC
    QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
  • 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_69ca834a4ea0819094970dceb9e389f3 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc4717f0e88190aaf0fd45bf726941 completed March 31, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69cef349d8408190bfd90a33a2d223bb completed April 2, 2026, 10:52 p.m.
Created at: March 30, 2026, 6:26 p.m.