Triple
T30636912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyberspace Administration of China |
E779865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internet regulator |
C12316
|
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 regulator Context triple: [Cyberspace Administration of China, instanceOf, internet regulator]
-
A.
telecommunications regulator
A telecommunications regulator is a governmental or independent authority responsible for overseeing, licensing, and enforcing rules in the communications sector to ensure fair competition, consumer protection, and efficient use of spectrum and infrastructure.
-
B.
media regulator
chosen
A media regulator is an authority or organization responsible for overseeing and enforcing rules, standards, and policies governing media content, ownership, and distribution to protect the public interest.
-
C.
national internet registry
A national internet registry is an organization responsible for allocating and managing internet number resources (such as IP addresses and AS numbers) within a specific country or territory, typically under the broader coordination of a regional internet registry.
-
D.
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.
-
E.
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.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:28 p.m.