Triple

T22814808
Position Surface form Disambiguated ID Type / Status
Subject RFC 8825 E565069 entity
Predicate references P771 FINISHED
Object RFC 8828 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 8828 | Statement: [RFC 8825, references, RFC 8828]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 8828
Context triple: [RFC 8825, references, RFC 8828]
  • A. RFC 8728
    RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
  • B. RFC 8078
    RFC 8078 is an Internet Engineering Task Force (IETF) standard that specifies guidelines and procedures for automatically signing DNSSEC delegations to improve the security and manageability of DNS.
  • 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 8881
    RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
  • E. RFC 8729
    RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
  • 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 8828
Target entity description: RFC 8828 is an IETF standard that specifies the WebRTC data channel establishment protocol using the Stream Control Transmission Protocol (SCTP) over DTLS.
  • A. RFC 8728
    RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
  • B. RFC 8078
    RFC 8078 is an Internet Engineering Task Force (IETF) standard that specifies guidelines and procedures for automatically signing DNSSEC delegations to improve the security and manageability of DNS.
  • 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 8881
    RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
  • E. RFC 8729
    RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
  • 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.