Triple
T2724311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Activities Board |
E60154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet governance body |
C172
|
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: Internet governance body Context triple: [Internet Activities Board, instanceOf, Internet governance body]
-
A.
internet governance concept
An internet governance concept is an abstract idea or framework that guides how the internet is managed, regulated, and shaped by technical, legal, economic, and social policies across diverse stakeholders.
-
B.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
Regional Internet Registry
A Regional Internet Registry is an organization responsible for allocating, registering, and managing Internet number resources (such as IP addresses and AS numbers) within a specific geographic region.
-
D.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
E.
affiliate of ICANN
An affiliate of ICANN is an organization or entity formally associated with the Internet Corporation for Assigned Names and Numbers to support its mission, programs, or policy development activities without being part of its core governing structure.
- F. None of above.
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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:55 p.m.