Triple
T22815166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF RMCAT Working Group |
E565077
|
entity |
| Predicate | relatedWorkingGroup |
P85663
|
FINISHED |
| Object | IETF RTCWEB Working Group |
—
|
NE NERFINISHED |
How this triple was built (2 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 RTCWEB Working Group | Statement: [IETF RMCAT Working Group, relatedWorkingGroup, IETF RTCWEB Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF RTCWEB Working Group Context triple: [IETF RMCAT Working Group, relatedWorkingGroup, IETF RTCWEB Working Group]
-
A.
IETF RTCWEB Working Group
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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.