Triple

T6034670
Position Surface form Disambiguated ID Type / Status
Subject IETF ICE Working Group E134386 entity
Predicate coordinatesWith P1140 FINISHED
Object IETF RTCWEB Working Group E24812 NE FINISHED

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 ICE Working Group, coordinatesWith, 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 ICE Working Group, coordinatesWith, 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 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.
  • 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 QUIC Working Group
    The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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.
Created at: March 22, 2026, 4:08 p.m.