Database Working Group
E831151
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Database Working Group canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T9933478 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
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.
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
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
RIPE community working group
ⓘ
technical policy working group ⓘ |
| collaboratesWith |
RIPE NCC
ⓘ
RIPE NCC Database Department ⓘ
linked to:
RIPE NCC
|
| communicationChannel | RIPE Database Working Group mailing list ⓘ |
| communityType | open, bottom-up, multi-stakeholder policy forum ⓘ |
| decisionMakingProcess | RIPE community consensus ⓘ |
| goal |
align RIPE Database behaviour with community requirements
ⓘ
ensure that RIPE Database policies remain up to date ⓘ ensure that the RIPE Database meets the operational needs of the RIPE community ⓘ improve quality of registration data in the RIPE Database ⓘ improve usability of the RIPE Database ⓘ |
| governs | RIPE Database usage policies ⓘ |
| hasChair | volunteer community chair or co-chairs ⓘ |
| influences | RIPE NCC implementation of RIPE Database services ⓘ |
| language | English ⓘ |
| meetingFrequency | twice per year at RIPE Meetings (typical) ⓘ |
| meetsAt |
RIPE Meetings
ⓘ
linked to:
RIPE Meeting
|
| membership | open to anyone in the RIPE community ⓘ |
| name | Database Working Group ⓘ |
| oversees |
policies for registration information of AS Numbers in the RIPE region
ⓘ
policies for registration information of IP address space in the RIPE region ⓘ |
| partOf |
RIPE NCC community structure
ⓘ
RIPE community ⓘ |
| region |
RIPE region
ⓘ
linked to:
RIPE NCC
|
| reportsTo | RIPE community ⓘ |
| responsibleFor |
RIPE Database policies
ⓘ
development of RIPE Database features at policy level ⓘ maintenance of RIPE Database functionality at policy level ⓘ technical aspects of the RIPE Database ⓘ |
| scope |
Internet number resource registration data in the RIPE region
ⓘ
RIPE Database ⓘ |
| shortName | DB-WG ⓘ |
| topic |
Internet number resource registration
ⓘ
RIPE Database object types and attributes ⓘ RIPE Database operational requirements ⓘ abuse contact and abuse-c handling in the RIPE Database ⓘ privacy and personal data in the RIPE Database at policy level ⓘ whois and RDAP-style registry services in the RIPE region ⓘ |
| website | https://www.ripe.net/participate/ripe/wg/db ⓘ |
| worksOn |
RIPE Database documentation requirements
ⓘ
RIPE Database object model and semantics ⓘ RIPE Database query mechanisms at policy and requirements level ⓘ RIPE Database update mechanisms at policy and requirements level ⓘ authorisation and authentication models for RIPE Database objects at policy level ⓘ data accuracy in the RIPE Database ⓘ data consistency in the RIPE Database ⓘ data security considerations for the RIPE Database at policy level ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Database Working Group Description of subject: 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.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.