Triple

T9933478
Position Surface form Disambiguated ID Type / Status
Subject RIPE community E192699 entity
Predicate hasWorkingGroup P1382 FINISHED
Object Database Working Group
The Database Working Group is a RIPE community group responsible for developing, maintaining, and improving policies and technical aspects of the RIPE Database, which stores registration information for Internet number resources in the RIPE region.
E831151 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: Database Working Group | Statement: [RIPE community, hasWorkingGroup, Database Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Database Working Group
Context triple: [RIPE community, hasWorkingGroup, Database Working Group]
  • A. Data Quality Working Group
    The Data Quality Working Group is a specialist body within the hydrographic community that develops and maintains standards, guidelines, and best practices for assessing and communicating the quality of hydrographic and marine geospatial data.
  • B. W3C Working Group
    A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
  • C. SPARQL Working Group
    The SPARQL Working Group is a W3C body responsible for developing and standardizing the SPARQL query language and related technologies for the Semantic Web.
  • D. Working Group on Digital Innovations
    The Working Group on Digital Innovations is a specialized body under the Committee on Payments and Market Infrastructures that analyzes and advises on the implications of emerging digital technologies for payment, clearing, and settlement systems.
  • E. 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.
  • 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: Database Working Group
Triple: [RIPE community, hasWorkingGroup, Database Working Group]
Generated description
The Database Working Group is a RIPE community group responsible for developing, maintaining, and improving policies and technical aspects of the RIPE Database, which stores registration information for Internet number resources in the RIPE region.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Database Working Group
Target entity description: The Database Working Group is a RIPE community group responsible for developing, maintaining, and improving policies and technical aspects of the RIPE Database, which stores registration information for Internet number resources in the RIPE region.
  • A. Data Quality Working Group
    The Data Quality Working Group is a specialist body within the hydrographic community that develops and maintains standards, guidelines, and best practices for assessing and communicating the quality of hydrographic and marine geospatial data.
  • B. W3C Working Group
    A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
  • C. SPARQL Working Group
    The SPARQL Working Group is a W3C body responsible for developing and standardizing the SPARQL query language and related technologies for the Semantic Web.
  • D. Working Group on Digital Innovations
    The Working Group on Digital Innovations is a specialized body under the Committee on Payments and Market Infrastructures that analyzes and advises on the implications of emerging digital technologies for payment, clearing, and settlement systems.
  • E. 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.
  • 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.