Triple
T31436154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratcliffe-on-Soar Power Station |
E801936
|
entity |
| Predicate | hasSecondaryFuel |
P67964
|
FINISHED |
| Object | natural gas |
—
|
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: natural gas | Statement: [Ratcliffe-on-Soar Power Station, hasSecondaryFuel, natural gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryFuel Context triple: [Ratcliffe-on-Soar Power Station, hasSecondaryFuel, natural gas]
-
A.
secondaryFuel
chosen
Indicates that an entity uses or is associated with a secondary (additional or backup) fuel source in addition to its primary fuel.
-
B.
hasFuelStorage
Indicates that one entity possesses or is equipped with a facility, container, or system used to store fuel for later use.
-
C.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
-
D.
hasFuel
Indicates that an entity possesses or contains fuel available for use.
-
E.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: April 30, 2026, 9:01 p.m.