Triple
T1808536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS over QUIC |
E40276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | encrypted transport protocol |
C995
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: encrypted transport protocol Context triple: [DNS over QUIC, instanceOf, encrypted transport protocol]
-
A.
cryptographic protocol
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
-
B.
network security protocol
chosen
A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
-
C.
encryption scheme
An encryption scheme is a systematic method that transforms readable data into an unreadable form using algorithms and keys to ensure confidentiality, integrity, and secure communication.
-
D.
transport layer protocol
A transport layer protocol is a communication protocol that provides end-to-end data transfer services between applications across networked devices, handling functions like segmentation, reliability, flow control, and multiplexing.
-
E.
crypt
A crypt is an underground chamber, typically beneath a church or cemetery, used for burials, storage of sacred relics, or as a place of remembrance for the dead.
- F. None of above.
Provenance (1 batch)
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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.