Triple

T35620367
Position Surface form Disambiguated ID Type / Status
Subject Davyhulme Sewage Works E1029292 entity
Predicate hasEnergyRecovery P44376 FINISHED
Object on-site power generation from sewage sludge 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: on-site power generation from sewage sludge | Statement: [Davyhulme Sewage Works, hasEnergyRecovery, on-site power generation from sewage sludge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEnergyRecovery
Context triple: [Davyhulme Sewage Works, hasEnergyRecovery, on-site power generation from sewage sludge]
  • A. energyRecoverySystem chosen
    Indicates that an entity is equipped with or utilizes a system designed to recover and reuse energy that would otherwise be lost.
  • B. usesEnergyFrom
    Indicates that one entity derives or consumes energy originating from another entity as its source.
  • C. usesEnergy
    Indicates that one entity consumes or relies on some form of energy to function, operate, or perform an action.
  • D. energyRecoveryRegulation
    Indicates a regulation that governs how energy is recovered, managed, or reused within a system or process.
  • E. hasEnergyInput
    Indicates that an entity receives or requires a specified source or form of energy to operate or occur.
  • 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_69f76e0709408190bbe322bf1707ef6b completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fd7b0503a08190ba07338365b6fcc9 completed May 8, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69fd7a9733dc81909199f453c0cc2bc1 completed May 8, 2026, 5:54 a.m.
Created at: May 3, 2026, 4:05 p.m.