Triple
T6034603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF MMUSIC Working Group |
E134384
|
entity |
| Predicate | collaboratesWith |
P37
|
FINISHED |
| Object |
IETF SIPCORE Working Group
The IETF SIPCORE Working Group is a standards body team within the Internet Engineering Task Force responsible for maintaining and developing the core specifications of the Session Initiation Protocol (SIP) used for real-time internet communications.
|
E565073
|
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 SIPCORE Working Group | Statement: [IETF MMUSIC Working Group, collaboratesWith, IETF SIPCORE Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF SIPCORE Working Group Context triple: [IETF MMUSIC Working Group, collaboratesWith, IETF SIPCORE Working Group]
-
A.
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.
-
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 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.
-
D.
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.
-
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 SIPCORE Working Group Triple: [IETF MMUSIC Working Group, collaboratesWith, IETF SIPCORE Working Group]
Generated description
The IETF SIPCORE Working Group is a standards body team within the Internet Engineering Task Force responsible for maintaining and developing the core specifications of the Session Initiation Protocol (SIP) used for real-time internet communications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IETF SIPCORE Working Group Target entity description: The IETF SIPCORE Working Group is a standards body team within the Internet Engineering Task Force responsible for maintaining and developing the core specifications of the Session Initiation Protocol (SIP) used for real-time internet communications.
-
A.
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.
-
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 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.
-
D.
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.
-
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
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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b33a7c8190ad6282286199b192 |
completed | March 22, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11388aec881908408d5844c96ea2d |
completed | March 23, 2026, 10:18 a.m. |
| NEDg | Description generation | batch_69c11689c0788190847435b526572edc |
completed | March 23, 2026, 10:31 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c116eb349c81908cad0bf5ccc458bc |
completed | March 23, 2026, 10:33 a.m. |
Created at: March 22, 2026, 4:08 p.m.