Triple
T28707594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utilities Act 2000 |
E729737
|
entity |
| Predicate | regulatorCreated |
P50234
|
FINISHED |
| Object | Ofgem |
—
|
NE NERFINISHED |
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: Ofgem | Statement: [Utilities Act 2000, regulatorCreated, Ofgem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatorCreated Context triple: [Utilities Act 2000, regulatorCreated, Ofgem]
-
A.
regulatorCreatedFor
Indicates that a regulatory body or authority was established specifically to oversee, manage, or enforce rules for a particular entity, activity, or domain.
-
B.
regulatorEstablished
chosen
Indicates that an entity has formally created, instituted, or set up a regulatory body or authority.
-
C.
regulatorAction
Indicates an action taken by a regulatory authority toward an entity, such as enforcing rules, issuing directives, or applying sanctions.
-
D.
regulatorRole
Indicates that one entity serves in an official capacity to oversee, control, or enforce rules and standards governing another entity or activity.
-
E.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an entity.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 5:46 a.m.