Triple
T32519551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Address Policy Working Group |
E831144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RIPE community working group |
C57954
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: RIPE community working group Context triple: [Address Policy Working Group, instanceOf, RIPE community working group]
-
A.
IETF working group
An IETF working group is a collaborative, time-bounded team of experts chartered within the Internet Engineering Task Force to develop, discuss, and standardize specific Internet technologies or protocols.
-
B.
IRTF research group
An IRTF research group is a collaborative team within the Internet Research Task Force that investigates long-term, exploratory topics related to the evolution and future of Internet technologies.
-
C.
Internet governance community
The Internet governance community is a diverse, multi-stakeholder group of individuals and organizations that collaboratively develop, influence, and implement policies, standards, and practices shaping the global Internet’s operation and evolution.
-
D.
IETF area
An IETF area is a high-level organizational division within the Internet Engineering Task Force that groups related working groups and activities under a common technical or functional theme.
-
E.
W3C Interest Group
A W3C Interest Group is a community of stakeholders within the World Wide Web Consortium that discusses and explores specific web-related topics, sharing use cases and requirements without necessarily producing formal technical standards.
- F. None of above. chosen
Provenance (1 batch)
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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.