Triple
T22814812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8825 |
E565069
|
entity |
| Predicate | references |
P771
|
FINISHED |
| Object |
RFC 8833
RFC 8833 is an Internet standards document that specifies considerations and mechanisms for using RTP over QUIC as a transport protocol for real-time media.
|
E1557290
|
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 8833 | Statement: [RFC 8825, references, RFC 8833]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8833 Context triple: [RFC 8825, references, RFC 8833]
-
A.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
B.
RFC 8831
RFC 8831 is an IETF standard that specifies the use of the Datagram Transport Layer Security (DTLS) protocol as the transport mechanism for Secure Real-time Transport Protocol (SRTP) in WebRTC.
-
C.
RFC 8838
RFC 8838 is an IETF specification that standardizes Trickle ICE, an extension to the ICE protocol that enables incremental, real-time gathering and exchange of connectivity candidates to speed up interactive connectivity establishment.
-
D.
RFC 8310
RFC 8310 is an IETF standard that specifies the use of Transport Layer Security (TLS) to provide privacy and integrity for DNS queries and responses.
-
E.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
- 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 8833 Triple: [RFC 8825, references, RFC 8833]
Generated description
RFC 8833 is an Internet standards document that specifies considerations and mechanisms for using RTP over QUIC as a transport protocol for real-time media.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8833 Target entity description: RFC 8833 is an Internet standards document that specifies considerations and mechanisms for using RTP over QUIC as a transport protocol for real-time media.
-
A.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
B.
RFC 8831
RFC 8831 is an IETF standard that specifies the use of the Datagram Transport Layer Security (DTLS) protocol as the transport mechanism for Secure Real-time Transport Protocol (SRTP) in WebRTC.
-
C.
RFC 8838
RFC 8838 is an IETF specification that standardizes Trickle ICE, an extension to the ICE protocol that enables incremental, real-time gathering and exchange of connectivity candidates to speed up interactive connectivity establishment.
-
D.
RFC 8310
RFC 8310 is an IETF standard that specifies the use of Transport Layer Security (TLS) to provide privacy and integrity for DNS queries and responses.
-
E.
RFC 4833
RFC 4833 is an Internet Engineering Task Force (IETF) document that specifies extensions to the Network Time Protocol (NTP) to support leap seconds and related timekeeping issues.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ba7a674908190a3d08c2c7210028e |
completed | May 18, 2026, 11:58 p.m. |
| NEDg | Description generation | batch_6a0ba82b00648190887a3164ececc66d |
completed | May 19, 2026, midnight |
| NED2 | Entity disambiguation (via description) | batch_6a0ba87ed5148190a96c0ea7e1cbb865 |
completed | May 19, 2026, 12:02 a.m. |
Created at: April 17, 2026, 3:33 p.m.