Triple
T13740412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Electricity Generating Board |
E330070
|
entity |
| Predicate | ownedAndOperated |
P105832
|
FINISHED |
| Object | large fossil-fuel power stations |
—
|
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: large fossil-fuel power stations | Statement: [Central Electricity Generating Board, ownedAndOperated, large fossil-fuel power stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedAndOperated Context triple: [Central Electricity Generating Board, ownedAndOperated, large fossil-fuel power stations]
-
A.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
B.
facilityOperatedBy
chosen
Indicates that a facility is managed, run, or controlled by a specified agent or organization.
-
C.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
D.
marketOperatedBy
Indicates that a market is managed, controlled, or run by a specific operator or organization.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0206a4b88190a60914e2b43e54f9 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.