Triple
T22814816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8825 |
E565069
|
entity |
| Predicate | references |
P771
|
FINISHED |
| Object | RFC 8837 |
—
|
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: RFC 8837 | Statement: [RFC 8825, references, RFC 8837]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8837 Context triple: [RFC 8825, references, RFC 8837]
-
A.
RFC 8836
RFC 8836 is an IETF standard that specifies congestion control requirements and considerations for real-time interactive media over RTP on the internet.
-
B.
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.
-
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 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.
-
E.
RFC 8927
RFC 8927 is an IETF specification that defines how to use JSON Schema for describing and validating YANG data models in network management.
- 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: RFC 8837 Target entity description: RFC 8837 is an IETF standard that specifies the use of RTP/RTCP multiplexing for WebRTC and related real-time communication systems to reduce the number of transport-layer flows.
-
A.
RFC 8836
RFC 8836 is an IETF standard that specifies congestion control requirements and considerations for real-time interactive media over RTP on the internet.
-
B.
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.
-
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 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.
-
E.
RFC 8927
RFC 8927 is an IETF specification that defines how to use JSON Schema for describing and validating YANG data models in network management.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
Created at: April 17, 2026, 3:33 p.m.