Triple
T311026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QUIC |
E7606
|
entity |
| Predicate | transportFor |
P11822
|
FINISHED |
| Object |
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.
|
E40276
|
NE FINISHED |
How this triple was built (5 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 (DoQ) | Statement: [QUIC, transportFor, DNS over QUIC (DoQ)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DNS over QUIC (DoQ) Context triple: [QUIC, transportFor, DNS over QUIC (DoQ)]
-
A.
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.
-
B.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
C.
IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
-
D.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: DNS over QUIC (DoQ) Triple: [QUIC, transportFor, DNS over QUIC (DoQ)]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DNS over QUIC (DoQ) Target entity description: 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.
-
A.
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.
-
B.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
C.
IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
-
D.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
E.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportFor Context triple: [QUIC, transportFor, DNS over QUIC (DoQ)]
-
A.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
B.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
C.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
D.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
E.
coordinatesTransportationServicesWith
Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
- F. None of above. chosen
Provenance (7 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea49636c8190a69cbd951fc0a4db |
completed | Feb. 28, 2026, 1:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3bc277528819096184b6cc6b98ae2 |
completed | March 1, 2026, 4:10 a.m. |
| NEDg | Description generation | batch_69a3bea16ee48190a033ea3907703e40 |
completed | March 1, 2026, 4:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a3befc80a8819092506dd29e18f2aa |
completed | March 1, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69a2e940b9e8819092b821ff17ed026b |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.