Triple

T20399887
Position Surface form Disambiguated ID Type / Status
Subject IBTA E500302 entity
Predicate hasWorkingGroup P1382 FINISHED
Object Technical 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: Technical Working Group | Statement: [IBTA, hasWorkingGroup, Technical Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Technical Working Group
Context triple: [IBTA, hasWorkingGroup, Technical Working Group]
  • A. Technical Committee
    The Technical Committee is Debian’s highest technical decision-making body, responsible for resolving technical disputes and making final rulings on matters of project architecture and policy.
  • B. Technical Coordination Group
    The Technical Coordination Group is a committee within the DVD Forum responsible for overseeing and harmonizing technical standards and specifications related to DVD technologies.
  • C. Working Group
    The Working Group is a category in the American Kennel Club classification system that includes large, strong dog breeds historically developed to perform tasks such as guarding, pulling, and rescue work.
  • D. Technical Advisory Committee
    The Technical Advisory Committee is a specialized expert body that provides technical guidance and support to the Caribbean Disaster Emergency Management Agency on disaster risk management and emergency response.
  • E. Technical Liaison Group
    The Technical Liaison Group is an ICANN-related body that facilitates coordination and communication between ICANN and key technical standards organizations in the Internet community.
  • 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: Technical Working Group
Target entity description: The Technical Working Group is a specialized committee within the InfiniBand Trade Association responsible for developing, reviewing, and maintaining the InfiniBand architecture’s technical specifications and standards.
  • A. Technical Committee
    The Technical Committee is Debian’s highest technical decision-making body, responsible for resolving technical disputes and making final rulings on matters of project architecture and policy.
  • B. Technical Coordination Group
    The Technical Coordination Group is a committee within the DVD Forum responsible for overseeing and harmonizing technical standards and specifications related to DVD technologies.
  • C. Working Group
    The Working Group is a category in the American Kennel Club classification system that includes large, strong dog breeds historically developed to perform tasks such as guarding, pulling, and rescue work.
  • D. Technical Advisory Committee
    The Technical Advisory Committee is a specialized expert body that provides technical guidance and support to the Caribbean Disaster Emergency Management Agency on disaster risk management and emergency response.
  • E. Technical Liaison Group
    The Technical Liaison Group is an ICANN-related body that facilitates coordination and communication between ICANN and key technical standards organizations in the Internet community.
  • 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_69e0b4a81bec8190b69adfdc1336a015 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6798db79c819085e3a2526538726f completed April 20, 2026, 7:07 p.m.
Created at: April 16, 2026, 11:29 a.m.