Triple
T31436167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratcliffe-on-Soar Power Station |
E801936
|
entity |
| Predicate | numberOfGeneratingUnits |
P112661
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Ratcliffe-on-Soar Power Station, numberOfGeneratingUnits, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfGeneratingUnits Context triple: [Ratcliffe-on-Soar Power Station, numberOfGeneratingUnits, 4]
-
A.
generatingUnitCount
chosen
Indicates the number of generating units associated with or involved in a given entity or context.
-
B.
generationUnits
Indicates a relationship where specific units or components are responsible for generating or producing something within a system or process.
-
C.
numberOfPowerhouses
Indicates the quantity of powerhouse entities associated with or contained by a given subject.
-
D.
mainGenerationCompanies
Indicates that the subject entity is one of the primary or principal companies responsible for generating (typically producing or supplying) a particular resource, product, or service.
-
E.
numberOfTurbines
Indicates the quantity of turbines associated with a given entity or installation.
- 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_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
Created at: April 30, 2026, 9:01 p.m.