Triple
T31436171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratcliffe-on-Soar Power Station |
E801936
|
entity |
| Predicate | hasFlueGasDesulfurization |
P171868
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ratcliffe-on-Soar Power Station, hasFlueGasDesulfurization, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlueGasDesulfurization Context triple: [Ratcliffe-on-Soar Power Station, hasFlueGasDesulfurization, yes]
-
A.
flueGasDesulfurizationCommissioned
chosen
Indicates that a flue gas desulfurization system has been put into operational service and formally commissioned for use.
-
B.
sulfurRecoveryProcess
Indicates a process in which sulfur is recovered or extracted, typically from industrial streams or waste gases.
-
C.
hasPersistentGasEmissions
Indicates that an entity continuously or repeatedly releases gaseous substances over an extended period.
-
D.
hasSulfurOdor
Indicates that an entity emits or possesses an odor characteristic of sulfur or sulfur-containing compounds.
-
E.
showsGasStripping
Indicates that one entity exhibits evidence of gas being removed or stripped away, typically due to external forces or interactions.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 9:01 p.m.