Triple

T22457292
Position Surface form Disambiguated ID Type / Status
Subject ICH Working Groups E555147 entity
Predicate hasSubgroup P747 FINISHED
Object Informal 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: Informal Working Group | Statement: [ICH Working Groups, hasSubgroup, Informal Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Informal Working Group
Context triple: [ICH Working Groups, hasSubgroup, Informal Working Group]
  • A. 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.
  • B. Joint Working Group
    The Joint Working Group is an ecumenical body that fosters dialogue and cooperation between the Roman Catholic Church and the World Council of Churches.
  • C. Working Group meeting
    A Working Group meeting is a formal gathering of experts and stakeholders who collaborate to develop, review, and refine technical standards and specifications within a specific domain.
  • D. Cooperation Working Group
    The Cooperation Working Group is a forum within the RIPE community that focuses on fostering collaboration and dialogue between technical stakeholders and public policy, governmental, and other Internet governance bodies.
  • E. Working Group B
    Working Group B is a technical body within the CTBTO Preparatory Commission responsible for developing and overseeing the verification regime and monitoring systems for the Comprehensive Nuclear-Test-Ban Treaty.
  • 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: Informal Working Group
Target entity description: The Informal Working Group is a specialized subgroup within the International Council for Harmonisation (ICH) framework that collaborates on focused regulatory or scientific topics prior to or alongside formal guideline development.
  • A. 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.
  • B. Joint Working Group
    The Joint Working Group is an ecumenical body that fosters dialogue and cooperation between the Roman Catholic Church and the World Council of Churches.
  • C. Working Group meeting
    A Working Group meeting is a formal gathering of experts and stakeholders who collaborate to develop, review, and refine technical standards and specifications within a specific domain.
  • D. Cooperation Working Group
    The Cooperation Working Group is a forum within the RIPE community that focuses on fostering collaboration and dialogue between technical stakeholders and public policy, governmental, and other Internet governance bodies.
  • E. Working Group B
    Working Group B is a technical body within the CTBTO Preparatory Commission responsible for developing and overseeing the verification regime and monitoring systems for the Comprehensive Nuclear-Test-Ban Treaty.
  • 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_69e11e51fdec8190adfdf9f8a6362221 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b7c428c8190847a259eef969525 completed April 29, 2026, 1:14 a.m.
Created at: April 16, 2026, 8:48 p.m.