Triple

T5480254
Position Surface form Disambiguated ID Type / Status
Subject RTP E123450 entity
Predicate definedIn P775 FINISHED
Object RFC 3550
RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
E523055 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 3550 | Statement: [RTP, definedIn, RFC 3550]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 3550
Context triple: [RTP, definedIn, RFC 3550]
  • A. RFC 5766
    RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
  • B. RFC 3711
    RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
  • C. RFC 3650
    RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
  • D. RFC 3530
    RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
  • E. RFC 3652
    RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
  • 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 3550
Triple: [RTP, definedIn, RFC 3550]
Generated description
RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 3550
Target entity description: RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
  • A. RFC 5766
    RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
  • B. RFC 3711
    RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
  • C. RFC 3650
    RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
  • D. RFC 3530
    RFC 3530 is the IETF specification that defines version 4 of the Network File System (NFSv4) protocol for file sharing over networks.
  • E. RFC 3652
    RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
  • 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd9248ca348190aa116cace0f9b07a completed March 20, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf48a2880c8190ad76cf8c3862aede completed March 22, 2026, 1:40 a.m.
NEDg Description generation batch_69bf4a95375881909ba730ad108eee8b completed March 22, 2026, 1:49 a.m.
NED2 Entity disambiguation (via description) batch_69bf4afb47a88190a66de6b6c7d5c241 completed March 22, 2026, 1:50 a.m.
Created at: March 20, 2026, 2:09 p.m.