Triple
T31436186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratcliffe-on-Soar Power Station |
E801936
|
entity |
| Predicate | plannedFutureUse |
P12134
|
FINISHED |
| Object | low-carbon energy hub (proposed) |
—
|
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: low-carbon energy hub (proposed) | Statement: [Ratcliffe-on-Soar Power Station, plannedFutureUse, low-carbon energy hub (proposed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFutureUse Context triple: [Ratcliffe-on-Soar Power Station, plannedFutureUse, low-carbon energy hub (proposed)]
-
A.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
potentialUse
Indicates that one entity could be used for, or is suitable for, a particular function, purpose, or application involving another entity.
-
C.
plannedFeature
Indicates that a particular feature is intended or scheduled to be developed or implemented in the future.
-
D.
plannedDevelopment
Indicates that one entity has been designated or scheduled for future development or construction by another entity.
-
E.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 30, 2026, 9:01 p.m.