Triple
T1808554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNS over QUIC |
E40276
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 9250
RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
|
E204175
|
NE FINISHED |
How this triple was built (4 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: RFC 9250 | Statement: [DNS over QUIC, definedInRFC, RFC 9250]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 9250 Context triple: [DNS over QUIC, definedInRFC, RFC 9250]
-
A.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
C.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
- 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: RFC 9250 Triple: [DNS over QUIC, definedInRFC, RFC 9250]
Generated description
RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 9250 Target entity description: RFC 9250 is an IETF standard that specifies how to run the Domain Name System (DNS) protocol over the QUIC transport for improved performance and privacy.
-
A.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
C.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 4250
RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
- F. None of above. chosen
Provenance (5 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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa6599f35c8190aefd20773365fdcf |
completed | March 6, 2026, 5:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adbf58cf648190a5a71adc82cfb618 |
completed | March 8, 2026, 6:26 p.m. |
| NEDg | Description generation | batch_69adc1daa59881909bcff0a07c01ad84 |
completed | March 8, 2026, 6:37 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adc27685f48190bdf2d5202a7f6934 |
completed | March 8, 2026, 6:39 p.m. |
Created at: March 4, 2026, 7:32 p.m.