Triple

T9933473
Position Surface form Disambiguated ID Type / Status
Subject RIPE community E192699 entity
Predicate hasWorkingGroup P1382 FINISHED
Object Anti-Abuse Working Group
The Anti-Abuse Working Group is a RIPE community body focused on developing policies, best practices, and guidance to prevent and address abuse of Internet resources within the RIPE NCC service region.
E831146 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: Anti-Abuse Working Group | Statement: [RIPE community, hasWorkingGroup, Anti-Abuse Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anti-Abuse Working Group
Context triple: [RIPE community, hasWorkingGroup, Anti-Abuse Working Group]
  • A. GNSO Working Groups
    GNSO Working Groups are collaborative teams within ICANN’s Generic Names Supporting Organization that develop and refine policies related to generic top-level domains through open, consensus-driven processes.
  • B. STORM Working Group
    The STORM Working Group is an IETF group focused on developing and standardizing protocols and extensions for storage over IP networks, particularly SCSI over RDMA and related technologies.
  • C. Advocacy Working Group
    The Advocacy Working Group is a specialized body within the International Competition Network that focuses on promoting pro-competition policies and enhancing awareness and understanding of competition law and policy among stakeholders worldwide.
  • D. Technical Assistance and Training Working Group
    The Technical Assistance and Training Working Group is a specialized body within the Egmont Group that develops and coordinates capacity-building and training initiatives to strengthen financial intelligence units’ effectiveness in combating money laundering and terrorist financing.
  • E. Working Group on Cyber Resilience
    The Working Group on Cyber Resilience is an expert body that develops international guidance and best practices to strengthen the cyber resilience of financial market infrastructures and related payment and settlement systems.
  • 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: Anti-Abuse Working Group
Triple: [RIPE community, hasWorkingGroup, Anti-Abuse Working Group]
Generated description
The Anti-Abuse Working Group is a RIPE community body focused on developing policies, best practices, and guidance to prevent and address abuse of Internet resources within the RIPE NCC service region.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Anti-Abuse Working Group
Target entity description: The Anti-Abuse Working Group is a RIPE community body focused on developing policies, best practices, and guidance to prevent and address abuse of Internet resources within the RIPE NCC service region.
  • A. GNSO Working Groups
    GNSO Working Groups are collaborative teams within ICANN’s Generic Names Supporting Organization that develop and refine policies related to generic top-level domains through open, consensus-driven processes.
  • B. STORM Working Group
    The STORM Working Group is an IETF group focused on developing and standardizing protocols and extensions for storage over IP networks, particularly SCSI over RDMA and related technologies.
  • C. Advocacy Working Group
    The Advocacy Working Group is a specialized body within the International Competition Network that focuses on promoting pro-competition policies and enhancing awareness and understanding of competition law and policy among stakeholders worldwide.
  • D. Technical Assistance and Training Working Group
    The Technical Assistance and Training Working Group is a specialized body within the Egmont Group that develops and coordinates capacity-building and training initiatives to strengthen financial intelligence units’ effectiveness in combating money laundering and terrorist financing.
  • E. Working Group on Cyber Resilience
    The Working Group on Cyber Resilience is an expert body that develops international guidance and best practices to strengthen the cyber resilience of financial market infrastructures and related payment and settlement systems.
  • 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_69ca82dd978c8190947124ab0d3315ac completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb5b89c808190a2e766025dd53bd5 completed April 2, 2026, 12:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69d228d1620c8190ac7125b268dd6832 completed April 5, 2026, 9:18 a.m.
NEDg Description generation batch_69d22c3a6fc0819083a376736325a04e completed April 5, 2026, 9:32 a.m.
NED2 Entity disambiguation (via description) batch_69d22cabf39881908f45667751384df5 completed April 5, 2026, 9:34 a.m.
Created at: March 30, 2026, 8:44 p.m.