Triple
T22814806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8825 |
E565069
|
entity |
| Predicate | references |
P771
|
FINISHED |
| Object | RFC 8826 |
—
|
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 8826 | Statement: [RFC 8825, references, RFC 8826]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8826 Context triple: [RFC 8825, references, RFC 8826]
-
A.
IETF RFC 8826
IETF RFC 8826 is a standards document that specifies the security considerations and requirements for real-time communication using WebRTC.
-
B.
RFC 8536
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
C.
RFC 8056
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- 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 8826 Target entity description: RFC 8826 is an IETF standards document that defines the security considerations and requirements for using WebRTC to enable secure real-time audio, video, and data communication over IP networks.
-
A.
IETF RFC 8826
chosen
IETF RFC 8826 is a standards document that specifies the security considerations and requirements for real-time communication using WebRTC.
-
B.
RFC 8536
RFC 8536 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier specifications to define the modern format and handling of time zone data in the Internet ecosystem.
-
C.
RFC 8056
RFC 8056 is an IETF specification that extends the Registration Data Access Protocol (RDAP) with support for RDAP object tags and other features to improve registration data management and retrieval.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- F. None of above.
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.