Triple
T22814995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF SIPCORE Working Group |
E565073
|
entity |
| Predicate | coordinatesWith |
P1140
|
FINISHED |
| Object | IETF STIR Working Group |
—
|
NE NERFINISHED |
How this triple was built (3 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 STIR Working Group | Statement: [IETF SIPCORE Working Group, coordinatesWith, IETF STIR Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF STIR Working Group Context triple: [IETF SIPCORE Working Group, coordinatesWith, IETF STIR Working Group]
-
A.
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.
-
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 DPRIVE working group
The IETF DPRIVE working group is a standards body team focused on developing and improving privacy-enhancing technologies for DNS, such as encrypted DNS protocols.
-
D.
IETF MASQUE Working Group
The IETF MASQUE Working Group is a standards body team within the Internet Engineering Task Force focused on developing protocols for proxying IP traffic and other network flows over HTTP.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IETF STIR Working Group Target entity description: The IETF STIR Working Group is an Internet Engineering Task Force group that develops standards to authenticate and verify caller identity in Internet telephony to combat spoofing and robocalls.
-
A.
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.
-
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 DPRIVE working group
The IETF DPRIVE working group is a standards body team focused on developing and improving privacy-enhancing technologies for DNS, such as encrypted DNS protocols.
-
D.
IETF MASQUE Working Group
The IETF MASQUE Working Group is a standards body team within the Internet Engineering Task Force focused on developing protocols for proxying IP traffic and other network flows over HTTP.
-
E.
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.
- F. None of above. chosen
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.