Triple
T8109110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Council of Television and Radio Broadcasting of Ukraine |
E189300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state regulatory authority |
C2929
|
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: state regulatory authority Context triple: [National Council of Television and Radio Broadcasting of Ukraine, instanceOf, state regulatory authority]
-
A.
state regulatory agency
chosen
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
B.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
C.
state government agency
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
D.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
E.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:32 p.m.