Triple
T14753838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pressurised water reactor |
E346679
|
entity |
| Predicate | thermalEfficiency |
P115662
|
FINISHED |
| Object | Moderate |
—
|
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: Moderate | Statement: [Pressurised water reactor, thermalEfficiency, Moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thermalEfficiency Context triple: [Pressurised water reactor, thermalEfficiency, Moderate]
-
A.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
B.
energyEfficiencyFeature
Indicates that an entity has a design, technology, or characteristic specifically intended to reduce energy consumption or improve energy performance.
-
C.
hasMaximumEfficiencyAt
Indicates that an entity reaches or exhibits its highest possible efficiency under a specified condition, context, or parameter value.
-
D.
fuelEfficiency
Indicates how effectively an entity uses fuel to perform a given amount of work or travel a certain distance.
-
E.
maximumEfficiency
Indicates that an entity operates at its highest possible level of performance or productivity under given conditions.
- F. None of above. chosen
Provenance (4 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.