Triple
T6034628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF AVTCORE Working Group |
E134385
|
entity |
| Predicate | coordinatesWith |
P1140
|
FINISHED |
| Object |
IETF RMCAT Working Group
The IETF RMCAT Working Group is a standards body group focused on developing congestion control algorithms and mechanisms for real-time interactive media over the internet, such as video conferencing and VoIP.
|
E565077
|
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 RMCAT Working Group | Statement: [IETF AVTCORE Working Group, coordinatesWith, IETF RMCAT Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF RMCAT Working Group Context triple: [IETF AVTCORE Working Group, coordinatesWith, IETF RMCAT 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 OPSAWG Working Group
The IETF OPSAWG Working Group is a standards body group within the Internet Engineering Task Force focused on developing and maintaining operational and management practices, guidelines, and related technologies for managing IP networks and services.
-
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.
IETF BEHAVE working group
The IETF BEHAVE working group was a standards body group within the Internet Engineering Task Force focused on defining and improving how Network Address Translators (NATs) interact with Internet protocols and applications.
- 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 RMCAT Working Group Triple: [IETF AVTCORE Working Group, coordinatesWith, IETF RMCAT Working Group]
Generated description
The IETF RMCAT Working Group is a standards body group focused on developing congestion control algorithms and mechanisms for real-time interactive media over the internet, such as video conferencing and VoIP.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IETF RMCAT Working Group Target entity description: The IETF RMCAT Working Group is a standards body group focused on developing congestion control algorithms and mechanisms for real-time interactive media over the internet, such as video conferencing and VoIP.
-
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 OPSAWG Working Group
The IETF OPSAWG Working Group is a standards body group within the Internet Engineering Task Force focused on developing and maintaining operational and management practices, guidelines, and related technologies for managing IP networks and services.
-
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.
IETF BEHAVE working group
The IETF BEHAVE working group was a standards body group within the Internet Engineering Task Force focused on defining and improving how Network Address Translators (NATs) interact with Internet protocols and applications.
- 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.