Triple
T33007202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIIO price control |
E844533
|
entity |
| Predicate | revenueFormula |
P57361
|
FINISHED |
| Object | allowed revenue linked to outputs and incentives |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: allowed revenue linked to outputs and incentives | Statement: [RIIO price control, revenueFormula, allowed revenue linked to outputs and incentives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revenueFormula Context triple: [RIIO price control, revenueFormula, allowed revenue linked to outputs and incentives]
-
A.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
B.
revenueUse
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
-
C.
revenueLevel
Indicates the relative amount or tier of revenue associated with an entity or activity.
-
D.
usesRevenueModel
Indicates that one entity applies or operates according to a particular revenue model to generate income.
-
E.
regulationFormula
chosen
Indicates the specific rule or formula that governs how a process, behavior, or quantity is controlled or regulated.
- F. None of above.
Provenance (3 batches)
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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:23 a.m.