Triple
T17080600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBMK-1000 |
E414458
|
entity |
| Predicate | reactorPowerElectrical |
P112586
|
FINISHED |
| Object | 1000 MWe |
—
|
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: 1000 MWe | Statement: [RBMK-1000, reactorPowerElectrical, 1000 MWe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorPowerElectrical Context triple: [RBMK-1000, reactorPowerElectrical, 1000 MWe]
-
A.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
B.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
C.
electricPowerOutput
chosen
Indicates the amount of electrical power produced or delivered by an entity.
-
D.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
E.
thermalCapacityPerReactor_MWth
Indicates the amount of thermal power capacity, measured in megawatts thermal (MWth), associated with each individual reactor.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.