Triple

T9191712
Position Surface form Disambiguated ID Type / Status
Subject RFC 4175 E220604 entity
Predicate publishedBy P80 FINISHED
Object IETF Audio/Video Transport (AVT) Working Group
The IETF Audio/Video Transport (AVT) Working Group is a standards body within the Internet Engineering Task Force responsible for developing protocols and specifications for real-time audio and video transmission over IP networks.
E134385 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: IETF Audio/Video Transport (AVT) Working Group | Statement: [RFC 4175, publishedBy, IETF Audio/Video Transport (AVT) Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IETF Audio/Video Transport (AVT) Working Group
Context triple: [RFC 4175, publishedBy, IETF Audio/Video Transport (AVT) Working Group]
  • A. IETF AVTCORE Working Group
    The IETF AVTCORE Working Group is a standards body team within the Internet Engineering Task Force responsible for maintaining and evolving the core RTP (Real-time Transport Protocol) specifications used for real-time audio, video, and related media over IP networks.
  • B. IETF MMUSIC Working Group
    The IETF MMUSIC Working Group is a standards body group within the Internet Engineering Task Force focused on developing protocols and formats for multimedia session control and negotiation, such as those used in real-time audio, video, and data communications.
  • C. IETF ICE Working Group
    The IETF ICE Working Group is a standards body team within the Internet Engineering Task Force responsible for developing and maintaining the Interactive Connectivity Establishment (ICE) protocols used for NAT traversal in real-time communications.
  • D. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • E. ITU-T Study Group 15
    ITU-T Study Group 15 is the International Telecommunication Union body responsible for developing global standards for transport, access, and home networking, including time and synchronization over packet networks.
  • 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: IETF Audio/Video Transport (AVT) Working Group
Triple: [RFC 4175, publishedBy, IETF Audio/Video Transport (AVT) Working Group]
Generated description
The IETF Audio/Video Transport (AVT) Working Group is a standards body within the Internet Engineering Task Force responsible for developing protocols and specifications for real-time audio and video transmission over IP networks.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: IETF Audio/Video Transport (AVT) Working Group
Target entity description: The IETF Audio/Video Transport (AVT) Working Group is a standards body within the Internet Engineering Task Force responsible for developing protocols and specifications for real-time audio and video transmission over IP networks.
  • A. IETF AVTCORE Working Group chosen
    The IETF AVTCORE Working Group is a standards body team within the Internet Engineering Task Force responsible for maintaining and evolving the core RTP (Real-time Transport Protocol) specifications used for real-time audio, video, and related media over IP networks.
  • B. IETF MMUSIC Working Group
    The IETF MMUSIC Working Group is a standards body group within the Internet Engineering Task Force focused on developing protocols and formats for multimedia session control and negotiation, such as those used in real-time audio, video, and data communications.
  • C. IETF ICE Working Group
    The IETF ICE Working Group is a standards body team within the Internet Engineering Task Force responsible for developing and maintaining the Interactive Connectivity Establishment (ICE) protocols used for NAT traversal in real-time communications.
  • D. IETF RTCWEB Working Group
    The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
  • E. ITU-T Study Group 15
    ITU-T Study Group 15 is the International Telecommunication Union body responsible for developing global standards for transport, access, and home networking, including time and synchronization over packet networks.
  • F. None of above.

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_69ca83e7ba70819088b74866d9da2c30 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd5c077b4819086c74e91ee4bd75e completed April 1, 2026, 8:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69d05c2bb2c481909db8c223aececf37 completed April 4, 2026, 12:32 a.m.
NEDg Description generation batch_69d05d4ec9d48190bb425fe0449f4bf2 completed April 4, 2026, 12:37 a.m.
NED2 Entity disambiguation (via description) batch_69d05ddd28008190b82c42220871e73f completed April 4, 2026, 12:39 a.m.
Created at: March 30, 2026, 7:24 p.m.