Triple
T11920061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinkley Point C nuclear power station |
E283628
|
entity |
| Predicate | estimatedCost_GBP |
P4259
|
FINISHED |
| Object | over 20 billion |
—
|
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: over 20 billion | Statement: [Hinkley Point C nuclear power station, estimatedCost_GBP, over 20 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedCost_GBP Context triple: [Hinkley Point C nuclear power station, estimatedCost_GBP, over 20 billion]
-
A.
estimatedCost
chosen
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
-
B.
estimatedDevelopmentCostCurrency
Indicates the currency in which the estimated development cost is expressed.
-
C.
estimatedCostComment
Indicates a textual note or explanation associated with an estimated cost, such as rationale, assumptions, or additional details about that estimate.
-
D.
constructionCostCurrency
Indicates the currency in which the construction cost of something is expressed.
-
E.
programCost
Indicates the monetary or resource expenditure required to implement, run, or participate in a particular program.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8dff77481908cacf6ad03df34ac |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.