Triple
T18302659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Service Fund contributions from telecommunications providers |
E438393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory financial obligation |
C19905
|
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: regulatory financial obligation Context triple: [Universal Service Fund contributions from telecommunications providers, instanceOf, regulatory financial obligation]
-
A.
administrative obligation
chosen
An administrative obligation is a duty imposed on individuals or organizations to complete specific formal procedures, filings, or compliance tasks required by governing authorities or institutional rules.
-
B.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
C.
federal obligation
A federal obligation is a legally binding duty or commitment imposed or recognized by the national government, typically involving the payment of money, provision of services, or compliance with regulatory requirements.
-
D.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
E.
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.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.