Triple
T22062015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2766 |
E545175
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | DNS Application Level Gateway |
—
|
NE NERFINISHED |
How this triple was built (3 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 Application Level Gateway | Statement: [RFC 2766, relatedTo, DNS Application Level Gateway]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DNS Application Level Gateway Context triple: [RFC 2766, relatedTo, DNS Application Level Gateway]
-
A.
DNS over HTTPS
DNS over HTTPS is a protocol that sends DNS queries and responses over encrypted HTTPS connections to enhance privacy and security.
-
B.
dnsop
dnsop is the IETF working group focused on the operational aspects, maintenance, and evolution of the Domain Name System (DNS).
-
C.
DNS Root Name Service Protocol and Deployment Requirements
"DNS Root Name Service Protocol and Deployment Requirements" is an IETF specification that defines the technical and operational requirements for the protocols and deployment practices used by the DNS root name service.
-
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.
DNS-based Authentication of Named Entities
DNS-based Authentication of Named Entities (DANE) is an Internet security protocol that uses DNSSEC to bind X.509 certificates to domain names, enabling secure TLS connections without relying solely on traditional certificate authorities.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DNS Application Level Gateway Target entity description: The DNS Application Level Gateway is a network function that inspects and modifies DNS traffic to support protocols like NAT-PT and ensure correct name resolution across differing IP address realms.
-
A.
DNS over HTTPS
DNS over HTTPS is a protocol that sends DNS queries and responses over encrypted HTTPS connections to enhance privacy and security.
-
B.
dnsop
dnsop is the IETF working group focused on the operational aspects, maintenance, and evolution of the Domain Name System (DNS).
-
C.
DNS Root Name Service Protocol and Deployment Requirements
"DNS Root Name Service Protocol and Deployment Requirements" is an IETF specification that defines the technical and operational requirements for the protocols and deployment practices used by the DNS root name service.
-
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.
DNS-based Authentication of Named Entities
DNS-based Authentication of Named Entities (DANE) is an Internet security protocol that uses DNSSEC to bind X.509 certificates to domain names, enabling secure TLS connections without relying solely on traditional certificate authorities.
- F. None of above. chosen
Provenance (2 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285d5e508190b3124a70fe55b32e |
completed | April 28, 2026, 9:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.