Triple
T9933472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIPE community |
E192699
|
entity |
| Predicate | hasWorkingGroup |
P1382
|
FINISHED |
| Object |
Routing Working Group
The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
|
E831145
|
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: Routing Working Group | Statement: [RIPE community, hasWorkingGroup, Routing Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Routing Working Group Context triple: [RIPE community, hasWorkingGroup, Routing Working Group]
-
A.
Routing Area Working Group
The Routing Area Working Group is an Internet Engineering Task Force (IETF) group responsible for developing and maintaining standards and guidelines related to Internet routing technologies and protocols.
-
B.
RFC Series Working Group
The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
-
C.
Network Working Group
The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
-
D.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
E.
IPng Working Group
The IPng Working Group was an IETF group responsible for designing and standardizing IPv6 as the successor to IPv4.
- 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: Routing Working Group Triple: [RIPE community, hasWorkingGroup, Routing Working Group]
Generated description
The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Routing Working Group Target entity description: The Routing Working Group is a RIPE community body that focuses on the development, coordination, and discussion of Internet routing policies, practices, and technologies within the RIPE region.
-
A.
Routing Area Working Group
The Routing Area Working Group is an Internet Engineering Task Force (IETF) group responsible for developing and maintaining standards and guidelines related to Internet routing technologies and protocols.
-
B.
RFC Series Working Group
The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
-
C.
Network Working Group
The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
-
D.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
E.
IPng Working Group
The IPng Working Group was an IETF group responsible for designing and standardizing IPv6 as the successor to IPv4.
- 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.