Triple
T5323796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LACTLD |
E121738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internet governance organization |
C999
|
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 organization Context triple: [LACTLD, instanceOf, internet governance organization]
-
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.
Internet governance role
An Internet governance role is a position responsible for shaping, implementing, or overseeing policies, standards, and decision-making processes that affect the operation, security, and evolution of the global internet.
-
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
chosen
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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.