Triple
T33078321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paks Nuclear Power Plant |
E846430
|
entity |
| Predicate | PaksIINetCapacityPerUnit |
P135437
|
FINISHED |
| Object | about 1200 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: about 1200 MWe | Statement: [Paks Nuclear Power Plant, PaksIINetCapacityPerUnit, about 1200 MWe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PaksIINetCapacityPerUnit Context triple: [Paks Nuclear Power Plant, PaksIINetCapacityPerUnit, about 1200 MWe]
-
A.
transmissionCapacity
Indicates the maximum amount of data or power that can be transmitted through a channel, link, or system over a given period.
-
B.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
C.
plannedCapacityMW
Indicates the intended or scheduled power generation capacity of an energy asset, measured in megawatts (MW).
-
D.
electricalCapacityPerReactor_MWe
chosen
Indicates the electrical power output capacity, measured in megawatts electric (MWe), that is provided by each individual reactor.
-
E.
installedCapacityUnit
Indicates the unit of measurement used to express the installed capacity associated with an 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:25 a.m.