Triple

T20399890
Position Surface form Disambiguated ID Type / Status
Subject IBTA E500302 entity
Predicate hasWorkingGroup P1382 FINISHED
Object Compliance and Interoperability Working Group
The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
E1428153 NE FINISHED

How this triple was built (4 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: Compliance and Interoperability Working Group | Statement: [IBTA, hasWorkingGroup, Compliance and Interoperability Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Compliance and Interoperability Working Group
Context triple: [IBTA, hasWorkingGroup, Compliance and Interoperability Working Group]
  • A. Rule Interchange Format Working Group
    The Rule Interchange Format Working Group is a W3C working group that developed standards for exchanging rules among different rule systems on the Semantic Web.
  • B. Information Exchange Working Group
    The Information Exchange Working Group is a specialized body within the Egmont Group that focuses on enhancing and facilitating secure international cooperation and information sharing among financial intelligence units to combat money laundering and related financial crimes.
  • C. Working Group on Evaluations and Compliance
    The Working Group on Evaluations and Compliance is a specialized body within the Financial Action Task Force responsible for assessing countries’ adherence to global anti–money laundering and counter-terrorist financing standards.
  • D. W3C Coordination Group
    The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
  • E. ENC Standards Maintenance Working Group
    The ENC Standards Maintenance Working Group is a specialist body responsible for developing, reviewing, and updating technical standards for Electronic Navigational Charts under the Hydrographic Services and Standards Committee.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Compliance and Interoperability Working Group
Triple: [IBTA, hasWorkingGroup, Compliance and Interoperability Working Group]
Generated description
The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Compliance and Interoperability Working Group
Target entity description: The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
  • A. Rule Interchange Format Working Group
    The Rule Interchange Format Working Group is a W3C working group that developed standards for exchanging rules among different rule systems on the Semantic Web.
  • B. Information Exchange Working Group
    The Information Exchange Working Group is a specialized body within the Egmont Group that focuses on enhancing and facilitating secure international cooperation and information sharing among financial intelligence units to combat money laundering and related financial crimes.
  • C. Working Group on Evaluations and Compliance
    The Working Group on Evaluations and Compliance is a specialized body within the Financial Action Task Force responsible for assessing countries’ adherence to global anti–money laundering and counter-terrorist financing standards.
  • D. W3C Coordination Group
    The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
  • E. ENC Standards Maintenance Working Group
    The ENC Standards Maintenance Working Group is a specialist body responsible for developing, reviewing, and updating technical standards for Electronic Navigational Charts under the Hydrographic Services and Standards Committee.
  • F. None of above. chosen

Provenance (5 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.
NED1 Entity disambiguation (via context triple) batch_6a08762bd7e881909ceddb1b3c26a914 completed May 16, 2026, 1:50 p.m.
NEDg Description generation batch_6a0877b7ed888190bccc1ba665528aca completed May 16, 2026, 1:57 p.m.
NED2 Entity disambiguation (via description) batch_6a087834ea1c8190b1b94c70a807668a completed May 16, 2026, 1:59 p.m.
Created at: April 16, 2026, 11:29 a.m.