Triple
T5533442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Domain Name Dispute Resolution Policy |
E145103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internet policy |
C1001
|
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 policy Context triple: [Uniform Domain Name Dispute Resolution Policy, instanceOf, internet policy]
-
A.
public policy domain
The public policy domain encompasses the processes, institutions, and frameworks through which governments and stakeholders identify societal issues, design and implement policy solutions, and evaluate their impacts on the public.
-
B.
internet governance concept
chosen
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.
-
C.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
D.
Internet service
An Internet service is a digital offering that provides users with specific online functionality or resources over a network, such as communication, data storage, or content access.
-
E.
intelligence law
Intelligence law is the body of legal rules, principles, and oversight mechanisms that govern the collection, analysis, sharing, and use of intelligence by state and related actors to protect national security while safeguarding rights and liberties.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:34 p.m.